Fabian Groffen wrote:
On 23-04-2008 15:40:32 -0400, McKennirey.Matthew wrote:
Thanks, yes we had ruled out JDBC and Merovingian on this.
We have only seen this on the recent build we took (2008-04-21 nightly=current) of v5.5.0 We did not experience it on earlier versions.
Feels related to a recent checkin of Martin: http://article.gmane.org/gmane.comp.db.monetdb.scm/5819 (and the other files modified in that commit)
those changes were committed on 23/4 not on 21/4 and not related to the error message. If you perform an cvs up of these changes it is adviced to recompile MonetDB5 from scratch, removing its build. This due to possible errors introduced by incomplete reference checking and old code files. I have to see the query (+schema) to understand what part of the query space is touched and not handled correctly. Don't hesitate to sent it.
------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javao... _______________________________________________ MonetDB-users mailing list MonetDB-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/monetdb-users