On Thursday, 26 May 2016 at 19:11:50 UTC, Stefan Koch wrote:
On Thursday, 26 May 2016 at 14:45:58 UTC, Suliman wrote:
Could you explain more details? What do you mean by
indirection work with data?
Sure, I can explain.
So, all that sqlite-d does is reading the sqlite-db files.
However the proper sqlite does much more:
It implements a whole ByteCode-Compiler and Interpreter to be
able to precompile and execute SQL-statements.
Thus even for simple querys you have a significant overhead.
If you want to use sqlite-d you basically write all your
queries as D code which can be directly executed, rather then
having to be compiled from SQL to ByteCode.
Oh! Look like for all time I misunderstood the purpose of your
project. Do you mean that your tool is created not for being SQL
compatible driver, but make possible to use D code for iteration
with DB?
And does it's mean that is not possible to write SQL-query with
this driver?
