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

Support :memory: or temporary databases #1492

Closed
ghost opened this issue Aug 5, 2018 · 12 comments
Closed

Support :memory: or temporary databases #1492

ghost opened this issue Aug 5, 2018 · 12 comments
Assignees

Comments

@ghost
Copy link

@ghost ghost commented Aug 5, 2018

Describe the new feature

Supporting a temporary database or the :memory: connection would be helpful when I just need to check something and don't actually need to persist changes.

Additional info

Please answer these questions before submitting your feature request.

Is your feature request related to an issue? Please include the issue number.

Does this feature exist in another product or project? Please provide a link.

https://www.sqlite.org/inmemorydb.html

DataGrip - but it's got its own issues with this

Do you have a screenshot? Please add screenshots to help explain your idea.

@justinclift
Copy link
Member

@justinclift justinclift commented Aug 5, 2018

Yeah. People have mentioned this a few times, and I personally tend to agree with you.

As long as it's easy to implement that is, and I reckon it probably would be. 😄

MKleusberg added a commit that referenced this issue Aug 5, 2018
Add a new menu option for opening an in-memory database. When working on
an in-memory database some menu options are disabled because they only
make sense when the database is also written to disk. I have left the
Write Changes button enabled though because for some actions the current
transaction needs to be committed - even though it's only committed to
memory then.

See issues #335 and #1492.
@MKleusberg
Copy link
Member

@MKleusberg MKleusberg commented Aug 5, 2018

I've just added a new menu option for this. Can you give tomorrow's nightly build a try (if you're on Windows or MacOS), @voltagex? 😄 I tried to tweak the code to handle the side effects this might have but maybe I have missed something 😉

@ghost
Copy link
Author

@ghost ghost commented Aug 10, 2018

After a very brief check this seems to work as expected.

@MKleusberg
Copy link
Member

@MKleusberg MKleusberg commented Aug 10, 2018

Thanks for checking, @voltagex! 😄 I'll close this issue then - if you should notice any problems with this in the future you can always open a new issue or reopen this one.

@torian257x
Copy link

@torian257x torian257x commented Jan 15, 2019

@MKleusberg what about linux?

@justinclift
Copy link
Member

@justinclift justinclift commented Jan 15, 2019

@Jossnaz For Linux, depending on your distribution you have a few options. 😄

Building it yourself is generally not too hard, but there is an occasional gotcha so YMMV.

Does that help? 😄

@torian257x
Copy link

@torian257x torian257x commented Jan 15, 2019

@justinclift the nightly build will contain as well the in :memory: access? i'm not sure how this project is built or if there are different versions for linux and windows.

@justinclift
Copy link
Member

@justinclift justinclift commented Jan 16, 2019

All of our nightly builds (regardless of OS), are done from our master branch. That's our development branch, which has the :memory: access stuff in it.

Sometimes the development branch is a bit flaky (eg just after we've added new features), but most of the time it's pretty good. It should be reasonable about now. 😄

@torian257x
Copy link

@torian257x torian257x commented Jan 16, 2019

@justinclift thaaanks justin <3

@justinclift
Copy link
Member

@justinclift justinclift commented Jan 16, 2019

No worries. 😄

@mgrojo
Copy link
Member

@mgrojo mgrojo commented Jan 16, 2019

@justinclift maybe that information about nightly builds for Linux should be added to https://nightlies.sqlitebrowser.org/latest/%2A%20README.txt too.

@justinclift
Copy link
Member

@justinclift justinclift commented Jan 16, 2019

Good thinking @mgrojo. 😄

Just cut-n-pasted the above text into a new "Linux" piece on the bottom of that. Should be good enough to start with.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
4 participants