Hi, our current literal expressions do not support directly longs, and this is very bad if you have longs in a db.
You create a literal with a long, say for example, Long.MAX_VALUE, it gets encoded into a double with reduced precision, and as a result the query that the sql encoders produce is incorrect. Adding Long support is a matter of having an extra constant into Expr.java, LITERAL_LONG, and have literal expression and sql encoders use it (easy, just look where LITERAL_INTEGER is used). It seems to me this is the kind of thing that should get into 2.3.x, and maybe even in 2.2.x since it does not break the external API. What do you think? Cheers Andrea ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Geotools-devel mailing list Geotools-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geotools-devel
