Anyone? What exactly is the problem with this? Is it just because the limit clause comes at the top of the query instead of at the end of the query? If so, wouldn't it be much easier to change it to appear at the end of the query?
Even though it may be a bug in MySql, it makes Jboss's EJB3 look bad because so many people depend on this type of functionality. Things like this tend to steer people away from this product towards other ones which can implement their needs better. It would probably take 1 or 2 lines of code to change the limit clause to appear at the bottom of the query. Then this problem (which has been lingering for 9 months without a resolution) could finally be resolved. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3919097#3919097 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3919097 ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 _______________________________________________ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
