Skip to content
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

Export Settings #5106

Open
GS2020-2020 opened this issue Nov 19, 2024 · 4 comments
Open

Export Settings #5106

GS2020-2020 opened this issue Nov 19, 2024 · 4 comments
Labels
enhancement New feature or request
Milestone

Comments

@GS2020-2020
Copy link

Details

Here you describe your problem details, or proposal for enhancement.

Ability to export settings

@pawelsalawa pawelsalawa added this to the 3.5.0 milestone Nov 19, 2024
@pawelsalawa pawelsalawa added the enhancement New feature or request label Nov 19, 2024
@marcpley
Copy link

marcpley commented Dec 8, 2024

So import settings too ?
When designing a DB using functions, it seems that those functions are not stored in the DB but in the settings. So a settings file must be added to the DB file for new users of the DB.
Is there a way to store the settings, or only the functions, in the DB ?

@pawelsalawa
Copy link
Owner

pawelsalawa commented Dec 8, 2024

@marcpley Do you ask whether Custom SQL Functions are stored in settings or in the DB? The answer is - they are stored in settings and it cannot be the other way around. SQLite does not support stored functions. There has to be application, which registers additional functions in the open, ongoing connection to the database. It's completely up to the application that uses SQLite database how these functions are executed. SQLiteStudio is executing them. They cannot be simply "transfered" to the target database and moved with database file, because execution engine of custom functions is in the application, not in the SQLite library.

@marcpley
Copy link

marcpley commented Dec 8, 2024

Ok, thanks for the clarification :-)
So we have to give a settings file with the DB file. If we can choose the name of the settings file it can have the same name of the DB file with a different ext.
And if we can import some settings but not all, it will be great, for example the functions and not the color theme :-)

@pawelsalawa
Copy link
Owner

Yes, I believe this is what this issue is about - to be able to export some settings (like functions) and then import them elsewhere.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants