There's a bit of confusion as to what I'm actually proposing. I can't reply to everyone so I'll just post the APIs and/or patches when they're done and we can argue those on their merits.
On Thu, Jun 4, 2015 at 5:03 PM, Darko Volaric <lists at darko.org> wrote: > Well, I've been using SQL for about 30 years so I'm unlikely to change my > view, but I think you bring up a much more important point: instead of > arguing online I should get back to work! > > > On Thu, Jun 4, 2015 at 4:11 PM, Richard Hipp <drh at sqlite.org> wrote: > >> On 6/4/15, Darko Volaric <lists at darko.org> wrote: >> > >> > What is motivating this for me is that I generate many unique queries >> in my >> > code for almost any operation. Converting those to SQL is error prone >> and >> > uses a lot of memory compared to the operation involved. The database >> > engine is so fast and efficient yet I'm wasting resources making SQL! >> > >> >> You are welcomed to go off and try to come up with a new and better >> interface. That's the beauty of open-source. Maybe you will come up >> with some new and innovative ideas that will change the industry! >> It's happened before! >> >> I just want to ensure that if, after working on your new approach for >> a while, you eventually decide that SQL isn't quite as bad a language >> as you originally thought it was, that you don't come back and say I >> didn't warn you. >> >> -- >> D. Richard Hipp >> drh at sqlite.org >> _______________________________________________ >> sqlite-users mailing list >> sqlite-users at mailinglists.sqlite.org >> http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users >> > >
