Now I feel blue!
-
FS15044 Insignia Blue[^], to be exact. I just knocked over my blue paint when painting the insignia on the belly side of the Huey. Looks like my pants now are insignia blue as well and I smell like a distillery because I thinned the paint with alcohol. Time to do something different. How about some coding? Normally I would use my good old Postgres database to hold the data, but this time I must do it in memory. The problem is that a full blown database would be overkill, but messing around with two dozen separate collections and enforcing relationships is too much fuzz. Does anybody know a nice library that can be used for that?
I have lived with several Zen masters - all of them were cats. His last invention was an evil Lasagna. It didn't kill anyone, and it actually tasted pretty good.
What's wrong with [SQLite](https://www.sqlite.org/index.html)? IIRC, It also supports in-memory databases.
Freedom is the freedom to say that two plus two make four. If that is granted, all else follows. -- 6079 Smith W.
-
Ahh, I see:
Quote:
RickZeeland contributor for a year
At first glance it is just what i need.
I have lived with several Zen masters - all of them were cats. His last invention was an evil Lasagna. It didn't kill anyone, and it actually tasted pretty good.
Now you are having a Slanted opinion :-\
-
What's wrong with [SQLite](https://www.sqlite.org/index.html)? IIRC, It also supports in-memory databases.
Freedom is the freedom to say that two plus two make four. If that is granted, all else follows. -- 6079 Smith W.
Just read this: In Search of Fast Local Storage – {coding}Sight[^] and you might think otherwise ...
-
FS15044 Insignia Blue[^], to be exact. I just knocked over my blue paint when painting the insignia on the belly side of the Huey. Looks like my pants now are insignia blue as well and I smell like a distillery because I thinned the paint with alcohol. Time to do something different. How about some coding? Normally I would use my good old Postgres database to hold the data, but this time I must do it in memory. The problem is that a full blown database would be overkill, but messing around with two dozen separate collections and enforcing relationships is too much fuzz. Does anybody know a nice library that can be used for that?
I have lived with several Zen masters - all of them were cats. His last invention was an evil Lasagna. It didn't kill anyone, and it actually tasted pretty good.
-
Just read this: In Search of Fast Local Storage – {coding}Sight[^] and you might think otherwise ...
1. The OP described a reasonably complex database, that requires maintenance and enforcement of relationships. This is just the kind of use case at which relational databases excel. 2. Speed, while important, is not the primary criterion for a database engine. Data and relationship integrity is. 3. When choosing between a mature database engine that is used in billions of devices and a relatively unknown engine, the mature product will usually win. Very few people can afford to bet their product (or their reputation) on unknown quantities. This does not mean that I would never try unknown products. It does mean that I will use them only in non-critical (i.e. non-production) environments until I am sure that (a) they can do what they claim to do and (b) are better in some significant way than the mature product.
Freedom is the freedom to say that two plus two make four. If that is granted, all else follows. -- 6079 Smith W.
-
1. The OP described a reasonably complex database, that requires maintenance and enforcement of relationships. This is just the kind of use case at which relational databases excel. 2. Speed, while important, is not the primary criterion for a database engine. Data and relationship integrity is. 3. When choosing between a mature database engine that is used in billions of devices and a relatively unknown engine, the mature product will usually win. Very few people can afford to bet their product (or their reputation) on unknown quantities. This does not mean that I would never try unknown products. It does mean that I will use them only in non-critical (i.e. non-production) environments until I am sure that (a) they can do what they claim to do and (b) are better in some significant way than the mature product.
Freedom is the freedom to say that two plus two make four. If that is granted, all else follows. -- 6079 Smith W.
That are some good points, SQLite is of course on the market for quite a long time and LiteDB undoubtedly still has some bugs as it is a relatively young product. So we will see what CodeWraith thinks of it (if he decides to use it). Exciting times! :-\
-
That are some good points, SQLite is of course on the market for quite a long time and LiteDB undoubtedly still has some bugs as it is a relatively young product. So we will see what CodeWraith thinks of it (if he decides to use it). Exciting times! :-\
I will try both of them. At the moment I can't yet sayhow much of a database I'm going to need. While I will have a few tables, I doubt that many of them will contain more than 1000 rows. Enforcing referential integrity is important, because I have come to rely on it as a safeguard against sloppy application logic. And my queries? They will not be very complex, as far as I can say at this early stage. Let's just wait and see where this leads to. Anyway, thanks for both suggestions.
I have lived with several Zen masters - all of them were cats. His last invention was an evil Lasagna. It didn't kill anyone, and it actually tasted pretty good.
-
I would prefer this one[^], but that would be a sinfully expensive toy[^].
I have lived with several Zen masters - all of them were cats. His last invention was an evil Lasagna. It didn't kill anyone, and it actually tasted pretty good.
-
FS15044 Insignia Blue[^], to be exact. I just knocked over my blue paint when painting the insignia on the belly side of the Huey. Looks like my pants now are insignia blue as well and I smell like a distillery because I thinned the paint with alcohol. Time to do something different. How about some coding? Normally I would use my good old Postgres database to hold the data, but this time I must do it in memory. The problem is that a full blown database would be overkill, but messing around with two dozen separate collections and enforcing relationships is too much fuzz. Does anybody know a nice library that can be used for that?
I have lived with several Zen masters - all of them were cats. His last invention was an evil Lasagna. It didn't kill anyone, and it actually tasted pretty good.
-
I've used sql ce for a couple of personal apps...works fine, but has limitations. (no views and windows only being big ones) If it's windoze only, there's always ms access. (the older free version)
"Go forth into the source" - Neal Morse
Thanks, but that does not help very much. I think that both will not work very well in a DirectX graphics context. :-) I have a homemade UI that needs some more development and I need something that provides the model part of the MVP pattern it is built around.
I have lived with several Zen masters - all of them were cats. His last invention was an evil Lasagna. It didn't kill anyone, and it actually tasted pretty good.
