Proposal: Database Engine for D
Piotrek via Digitalmars-d
digitalmars-d at puremagic.com
Mon Jan 4 09:18:06 PST 2016
On Sunday, 3 January 2016 at 19:48:42 UTC, Abdulhaq wrote:
> My two pence, if you want it to be fast then it must have a
> good implementation of indices. Your filter functions should
> not actually start collecting real records, but instead should
> simply change the way that the cursor traverses the underlying
> data store. You will need good query 'compilation' like the big
> boys do, which work out which tables and indices to use and in
> which order, based on stats of the data / indices.
Agree (I mentioned about proxies before). But I'm not sure about
"good query compilation" thing. Good storage management should
do. Rest can be done in user code.
> If you want ACID then SQL seems like a good approach to me,
> certainly I wouldn't want anything ORM-like for updating /
> inserting data.
Well. Some people really like SQL. I'm not one of them. I'm
neither a fan of ORM+SQL. But I think ACID is not only reserved
for SQL.
> There a number of good libraries out there already, SQLite
> obviously springs to mind.
The SQLite project is great.
> It would be a fun project but perhaps a lot more work than you
> realised if you really want isolation levels, speed etc.
Yes, I know. But one step at a time. It's a some kind of fun for
me as well ;)
Cheers
Piotrek
More information about the Digitalmars-d
mailing list