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

in-memory sqlite #335

Closed
tbayart opened this issue Jun 3, 2015 · 11 comments
Closed

in-memory sqlite #335

tbayart opened this issue Jun 3, 2015 · 11 comments
Assignees
Labels
enhancement Feature requests.

Comments

@tbayart
Copy link

tbayart commented Jun 3, 2015

Beside me, anyone else could find useful to be able to open an in-memory sqlite database ?
https://www.sqlite.org/inmemorydb.html

@glawrence
Copy link
Contributor

I understand the advantages of in-memory databases, however you will notice on that web page that "all database connections sharing the in-memory database need to be in the same process". This means you could create a database in DB4S but it would not be available to any other process and DB4S could not open one belonging to another process. So adding this feature would seem to me to be of limited use. However if you can help explain a good use case or you want to add this yourself via a pull request then please, fire away.

@tbayart
Copy link
Author

tbayart commented Jun 4, 2015

I know you can't open an existing in-memory database.
I was thinking this could be useful for testing purpose only.
Instead of creating a database file which need to be dropped / deleted when you want to test something else or test a database generation script.
Not a priority enhancement, I admit 😉

@glawrence
Copy link
Contributor

Right, okay, I see what you mean now, thanks for explaining. Are you able to implement this yourself?

@glawrence glawrence added the enhancement Feature requests. label Jun 4, 2015
@tbayart
Copy link
Author

tbayart commented Jun 4, 2015

Maybe, need to take time and look into the code.
Btw, is there a howto build/compile DB4S somewhere ?
or at least a "required" list of things I need to be able to build it ?
I work with visual studio 2013 community

@justinclift
Copy link
Member

@tbayart There is https://github.com/sqlitebrowser/sqlitebrowser/blob/master/BUILDING.md, which is supposed to have all of the building info in it.

I think it's out of date for Windows though, having only the previous approach listed (cross compiling from Linux using MXE). @rp- has been working on a new build process using Visual Studio, but I don't think it's documented yet. That being said, it may not be too hard to figure out (unsure).

@tbayart
Copy link
Author

tbayart commented Jun 4, 2015

Thanks for the link
I will check and report

@justinclift
Copy link
Member

@glawrence We should probably get the initial Windows building instructions onto the wiki, see if we can find people to test them out/fix/tweak/whatever as needed so they're correct, then possibly add them to BUILDING.md.

Any interest in getting that started, then making a call out through Twitter (main DB4S account) or similar for people to help with them? 😄

@glawrence
Copy link
Contributor

As per my other recent comment, yes we should and I will have a go at this as soon as I get time, which I hope is actually soon!

@justinclift
Copy link
Member

Awesome. Hoping so too. 😉

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

Are you still around, @tbayart? It's been a long time but we finally added a new menu option for this 😄 If you're still interested, can you give tomorrow's nightly build a try and see if it works for you?

@MKleusberg
Copy link
Member

I'll close this issue because the in-memory databases have been confirmed to work in #1492 and we have way too many open issues at the moment 😉 But if you should notice any problems with this or if I have missed something, please just just reopen this issue, @tbayart 😄

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

No branches or pull requests

4 participants