Hi all,
What this bug means is that two semantically identical SQL requests give two different results in MonetDB:
- in request A, we have a statement saying:
where a.col = 'VAL' and b.col = 'VAL'
- in request B, we have:
where a.col = b.col and a.col = 'VAL'
Both should give the same result... but they don't. Another variant is that removing a "where a.another = 'AVALUE' " from the request makes it work as expected (the data in the table happens to always respect this statement). So simplifying slightly the request makes MonetDB compute the right result...
The bug report now contains a dump of the tables that are used in the requests, so this can be easily reproduced...
Any idea anyone ?
Franck
Full Disclosure: I am working with Matthieu on the same project. The requests are generated by Mondrian ROLAP engine, and work as expected on both Postgresql and Oracle.
_______________________________________________ users-list mailing list users-list@monetdb.org http://mail.monetdb.org/mailman/listinfo/users-list