Hello ! It seems that you mix apples to oranges and try to compare then.
One thing is formal grammar/syntax and the other is implementation/optimization/execution. The fact that sqlite does things in one way now do not mean it's the best/definitive way of implement things and that can be changed. We are not going against anyone here we are discussing the way thins are/have been done and questioning the reason of it and possible alternatives for the same/different outcomes. All of it towards a more friendly/useful tool, but it seems that you fell attacked and try to negate most propositions with sometimes naive arguments. Relax and try to see the reasons behind other peoples view. Let's be friends! Cheers ! > Sat Sep 05 2015 8:55:55 pm CEST CEST from "Simon Slavin" ><slavins at bigfraud.org> Subject: Re: [sqlite] Third test of json and index >expressions, now it works > > On 5 Sep 2015, at 7:07pm, Darko Volaric <lists at darko.org> wrote: > > >>That's not a valid reason since it's trivial for SQLite to transform >> aliases by substituting their names with their definitions. It could be >> handled in the parser code. >> > And by doing that you would not get optimization, since SQLite would have >to work out the value once for the WHERE clause and once for the selected >value. Which is what SQLite does now. Which is what you are complaining about >in this thread. > > Remember: SQLite /does/ do this, even though it's not required by the SQL >standard. > > Simon. > _______________________________________________ > sqlite-users mailing list > sqlite-users at mailinglists.sqlite.org > http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users > > > ?
