|
|
|
How does/did the problem manifest itself ?
The problem shows up, if you execute queries like "... where id between $2 and
$1": If the bind variables are not used in ascending order, their values are used in the wrong order. ("... between $1 and $2" in this case" Martin, your patch includes code that has been posted as part of bug 1788. Can
you please remove this from and repost the patch ? Well, I didn't know, which of the bug reports you would process first, so they
contain partially the same test cases. Let's wait until after commiting of bug 1788, and then separate the two patches. Bug 1788 has been committed. Time for a spring-time cleaning session ..
![]() Just marking this bug (eventually) as fixed ..
![]() Martin, a fresh patch would be something absolutely tasty ..
![]() Created an attachment (id=789)
updated patch OK, here is the patch without the already committed parts. And now with setting the state of this bug to 'fixed' .. ;-(.
|
proposed patch including CTF tests for basic OQL queries