-
Notifications
You must be signed in to change notification settings - Fork 3.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
before 24.0 it was portable #28259
Comments
It was always like this. DBeaver stores its data inside the |
After 24.0 its creating a folder install-data and saves there office and
svg plugins. İt wasnt so before
Thanks for reply
29 Nis 2024 Pzt 02:20 tarihinde ShadelessFox ***@***.***>
şunu yazdı:
… It was always like this. DBeaver stores its data inside the
%APPDATA%\DBeaverData folder. Was it different for you? What distribution
do you use?
—
Reply to this email directly, view it on GitHub
<#28259 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BIECOR5U37R2IHQM7VI2MYLY7V72BAVCNFSM6AAAAABG4UJR5GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOBRGY4TINRWGY>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Previously, it would store data from this directory in your user home directory. Now, it's unified, and all DBeaver-related data is stored in one place. |
But with this change we cant use it portable right now. Before we moved
only c:/dbeaver folder to other computer and plugins was working
succesfully. Now it s not..
29 Nis 2024 Pzt 02:27 tarihinde ShadelessFox ***@***.***>
şunu yazdı:
… Previously, it would store data from this directory in your user home
directory. Now, it's unified, and all DBeaver-related data is stored in one
place.
—
Reply to this email directly, view it on GitHub
<#28259 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BIECOR5GMHF357VNUPDAZATY7WAX5AVCNFSM6AAAAABG4UJR5GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOBRGY4TMOJQGQ>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Now I understand what you're talking about. Thanks for the report. |
You can workaround this issue by adding the following line to the end of the -Dosgi.configuration.area=.\configuration Please let me know it it helps. |
It doesnt work. I get this error. (I sent as at attachment)
29 Nis 2024 Pzt 13:12 tarihinde ShadelessFox ***@***.***>
şunu yazdı:
… You can workaround this issue by adding the following line to the end of
the dbeaver.ini file:
-Dosgi.configuration.area=.\configuration
Please let me know it it helps.
—
Reply to this email directly, view it on GitHub
<#28259 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BIECOR7VVP3ST6DW2774DQ3Y7YMKFAVCNFSM6AAAAABG4UJR5GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOBSGM2DQOJZGI>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
You can't attach files by email. Please reply directly on GitHub. |
Try reinstalling DBeaver and do this #28259 (comment) before even launching it. |
Nothing changed still i got same message :(
29 Nis 2024 Pzt 15:35 tarihinde ShadelessFox ***@***.***>
şunu yazdı:
… Try reinstalling DBeaver and do this #28259 (comment)
<#28259 (comment)>
before even launching it.
—
Reply to this email directly, view it on GitHub
<#28259 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BIECOR6HCSQH6ZFYHGJ6YTTY7Y5AZAVCNFSM6AAAAABG4UJR5GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOBSGYYTMNRWHA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Hello @Yigitttttttt, first thanks for your request, but I see here mixed issues:
|
Can we make it what it was in the previous versions to solve the problem?
7 May 2024 Sal 14:39 tarihinde Sergei Kovalchuk ***@***.***>
şunu yazdı:
… Hello @Yigitttttttt <https://github.com/Yigitttttttt>, first thanks for
your request, but I see here mixed issues:
1. Portable product version ( location of configuration should be in
the same location for the zipped product version)
2. Additional plugin installation, There are no clear steps for
reproducing.
—
Reply to this email directly, view it on GitHub
<#28259 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BIECORYYBNNZH7AYOL2JGM3ZBC4PNAVCNFSM6AAAAABG4UJR5GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOJYGIYDGMJRGM>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
It's a little more complicated. |
Now we can no longer use the new versions...
7 May 2024 Sal 14:53 tarihinde ShadelessFox ***@***.***> şunu
yazdı:
… It's a little more complicated.
—
Reply to this email directly, view it on GitHub
<#28259 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BIECOR6JUDD3JZVLYCXBKV3ZBC6D3AVCNFSM6AAAAABG4UJR5GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOJYGIZDMOJXGQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
This ticket is scheduled for the current milestone. The fix will be available in two weeks. |
Thank you
7 May 2024 Sal 15:06 tarihinde ShadelessFox ***@***.***> şunu
yazdı:
… This ticket is scheduled for the current milestone. The fix will be
available in two weeks.
—
Reply to this email directly, view it on GitHub
<#28259 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BIECOR3HB2DR7CADOHQY5FDZBC7UZAVCNFSM6AAAAABG4UJR5GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOJYGI2TCOBQGE>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Fix for identify install location and configuration location
I have another urgent problem, is it possible to get it done in two weeks? |
Hi,
we're using Dbeaver in a virtual maschine, bcoz of this we need to have a portable version (the network is closed we just put Dbeaver folder) before 24.0 version it was so and the life was easy. after version 24.0 Office etc. addins saving in folder users/dbeaverdata/instal-data or something like this.. it makes harder using the Dbeaver portable. Please could you do like before this feature.
Thank you
(sorry for my English)
The text was updated successfully, but these errors were encountered: