Hmm, MSSQL doesn't support native limits (unless you count some "TOP" tricks.) I never noticed the DB Adapter was set to true. That's probably the reason that LargeSelect fails in the test project. (FWIW, This has been in bugs to fix list for a while, with a low priority... Thanks TV). I'll check check it out, but it won't be for at least a week from Tuesday. I'm going to be a beach bum with only dial up access all next week. Then gotta play catchup with the real world when I get back... One of these days I'll find a good paying job who's Job Title is Beach Bum...
________________________________ From: Thomas Vandahl [mailto:[EMAIL PROTECTED] Sent: Sat 7/8/2006 4:49 AM To: Apache Torque Developers List Subject: Re: svn commit: r419657 - /db/torque/runtime/trunk/src/java/org/apache/torque/adapter/ Thomas Fischer wrote: > Thomas, > > are you sure about the change to DBMSSQL ? It extends DbSybase (which is > bad in my opinion), and you removed the redefinition of > supportsNativeLimit from true to false, which changes the behaviour of > DBMSSQL That's right. Concerning the extension of DBSybase: "It was like this when I got here" :-) The other change: I remember Greg having difficulties with LargeSelect and MS-SQL. Citing the JavaDoc of Query.setRowCount(): /** * Set the rowcount number. This is used to limit the number of * rows returned by Sybase and MS SQL/Server. * * @param rowcount A String. */ I thought it might be a good idea to make this feature available. It was one of the places where getLimitStyle() and supportsNativeLimit() were sending inconsistent messages. This should be fixed now. Greg, would you mind checking this out, just to be sure? Bye, Thomas. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Duke CE Privacy Statement Please be advised that this e-mail and any files transmitted with it are confidential communication or may otherwise be privileged or confidential and are intended solely for the individual or entity to whom they are addressed. If you are not the intended recipient you may not rely on the contents of this email or any attachments, and we ask that you please not read, copy or retransmit this communication, but reply to the sender and destroy the email, its contents, and all copies thereof immediately. Any unauthorized dissemination, distribution or copying of this communication is strictly prohibited.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
