> On Nov 10, 2014, at 9:31 AM, Richard Hipp wrote:
>
> On Mon, Nov 10, 2014 at 12:28 PM, Ward Willats
> wrote:
>
>>
>>> On Nov 10, 2014, at 3:11 AM, Richard Hipp wrote:
>>>
>>> If you recompile the SQLite command-line shell
On Mon, Nov 10, 2014 at 12:28 PM, Ward Willats
wrote:
>
> > On Nov 10, 2014, at 3:11 AM, Richard Hipp wrote:
> >
> > If you recompile the SQLite command-line shell (sqlite3.exe) using the
> > -DSQLITE_ENABLE_SELECTTRACE option, then you can enter:
> >
>
> On Nov 10, 2014, at 3:11 AM, Richard Hipp wrote:
>
> If you recompile the SQLite command-line shell (sqlite3.exe) using the
> -DSQLITE_ENABLE_SELECTTRACE option, then you can enter:
>
If I do that,
gcc -D SQLITE_ENABLE_SELECTTRACE -D HAVE_READLINE -l readline -o
On 11/10/2014 4:40 AM, Prakash Premkumar wrote:
=
/\
salary+
/ \
3 3
/
*
/
On Mon, Nov 10, 2014 at 4:40 AM, Prakash Premkumar
wrote:
> The where clause in sqlite is encoded as a tree
>
> Let's say I have select statement like :
>
> SELECT * from employee where salary = 3+5*4+3;
>
> The tree which takes care of operator precedence is :
>
>
On 10 Nov 2014, at 9:40am, Prakash Premkumar wrote:
> If I am constructing this tree for where clause by myself, should i take
> the operator precedence in to account while constructing it or will sqlite
> take care of precedence,given any tree (i.e constructing it with
>From a mathematical standpoint in your example, going back to grade 4 math
(35 years ago for me. *sigh*. I'm so sad), where clause works based
off of standard order of operations based on BEDMAS and eventually working
things down to booleans. In your example, the math would be processed as
Your tree is wrong. I would expect that operator precedence is handled in the
parser. The code generator will happily implement any tree, regardless of how
insane it may be.
-Ursprüngliche Nachricht-
Von: Prakash Premkumar [mailto:prakash.p...@gmail.com]
Gesendet: Montag, 10. November
8 matches
Mail list logo