I agree with you, and am not suggesting getting rid of it, but rather making it "pluggable" like many parts of the back end.
Right now, roughly speaking, I'm doing: logical form -> SQL -> execution of logical form, and SQL seems to me to just be an arbitrary hoop that I have to jump through, complicating things along the way. Obviously this is not terribly mainstream, but I think would greatly improve the usefulness and structure of SQLite. Just my 2 cents on the subject... On Wed, Feb 18, 2015 at 11:43 AM, Richard Hipp <drh at sqlite.org> wrote: > On 2/18/15, Darko Volaric <lists at darko.org> wrote: > > The only thing I'd change about SQLite is the SQL bit. > > Most people agree that the SQL language is a bit of a mess. But so is > the Qwerty keyboard layout. The problem is that the improvement you > get by moving to something else is less than the pain of making the > move. Everybody agrees that Dvorak is a better keyboard layout, and > yet nobody uses Dvorak even though it has been widely available on > computer keyboards since the Apple-II, Not intending to rain on your > parade, but I think the truth is we are probably stuck with SQL for a > while yet. > > -- > 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 >
