sqlite3 vs. sqlite-d

[Stefan Koch via Digitalmars-d]

On Thursday, 8 June 2017 at 13:06:55 UTC, Ozan (O/N/S) wrote:
> Your sqlite-d solution would be complete if writing sqlite 
> files are also possible. Ignore the SQL parsing stuff, it does 
> not fit in a world of fast data processing.

Writing or rather modifying sqlite-dbs is a bit harder then 
reading them.
Since the B-Tree should not get to imbalanced.

I started on write support a while back, but at that time I did 
not understand the structure well enough to guarantee efficient 
write-support. (which would also require you to keep the index 
updated and so on ...)

As for parsing sql.
Unfortunately the column information is stored in form of a 
create table statement which forces me to parse at-least that 
much sql.
In order to provide a nice interface in which you don't have to 
look up the position of your columns manually.