[#TORQUE-87] incorrect select query is created if offset is set but limit is not set in mysql and postgresql

Torque

Created: 24/Mar/07 03:55 PM Updated: 24/Mar/07 04:05 PM

Return to search

Component/s:

Runtime

Affects Version/s:

3.3-RC2

Fix Version/s:

3.3-RC3

Time Tracking:

Not Specified

Environment:

mysql or postgresql

Resolution Date:

24/Mar/07 04:05 PM

Description

« Hide

In both cases, the limit is set to -1 in the created sql, which leads to wrong results

All

Comments

Work Log

Change History

Subversion Commits

Sort Order:

Repository	Revision	Date	User	Message
ASF	#522044	Sat Mar 24 16:00:57 UTC 2007	tfischer	- Fixed handling of select statements in mysql and postgresql if offset is set but limit is not set in a query. - replaced tabs by spaces in DataTest.java Fixes ~~TORQUE-87~~
				Files Changed
				MODIFY /db/torque/site/trunk/xdocs/changes.xml MODIFY /db/torque/runtime/trunk/src/java/org/apache/torque/adapter/DBMM.java MODIFY /db/torque/runtime/trunk/src/java/org/apache/torque/util/Query.java MODIFY /db/torque/runtime/trunk/src/java/org/apache/torque/adapter/DBPostgres.java MODIFY /db/torque/test/trunk/test-project/src/java/org/apache/torque/DataTest.java

Repository	Revision	Date	User	Message
ASF	#523914	Fri Mar 30 02:45:20 UTC 2007	seade	Updated for ~~TORQUE-87~~ changes.
				Files Changed
				MODIFY /db/torque/runtime/trunk/src/test/org/apache/torque/util/CriteriaTest.java