Closed GoogleCodeExporter closed 9 years ago
THis is not a problem of the position calculator, it is a problem of the
parsing algorithm. "password" is a reserved keyword, so the parser doesn't
interpret it as column. If you parse the statement without position calculation
and print the result, you will see a very strange result set.
Original comment by pho...@gmx.de
on 1 Jun 2012 at 6:07
I have added some code to prevent PASSWORD as extra keyword, if it doesn't
follow after a SET statement. But PASSWORD is also a function and the parser
has no chance to differ between function and column. So the resultset is wrong
on that point.
Check out REV 284.
Original comment by pho...@gmx.de
on 1 Jun 2012 at 6:35
Maybe I can split the function array into functions with/without parameters. So
I can look forward, if there are some parameters and differ between a simple
colref and a function. This will not work on functions like NOW without
parenthesis. But it help in some other cases.
Original comment by pho...@gmx.de
on 1 Jun 2012 at 6:40
Check out r345, if have added some code to handle that issue. There are some
tests, which runs fine.
Original comment by pho...@gmx.de
on 30 Aug 2012 at 8:01
Original comment by pho...@gmx.de
on 1 Nov 2013 at 11:08
Original issue reported on code.google.com by
h.leith...@gmail.com
on 29 May 2012 at 3:16Attachments: