[
https://issues.apache.org/jira/browse/TORQUE-92?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Vandahl resolved TORQUE-92.
--
Resolution: Fixed
Added the call to BasePeer.correctBooleans() to LargeSelect.
Fixed the handlin
Henning P. Schmiedehausen wrote:
> I'd like to warn you that we will release (we already voted, tagged,
> rolled and deployed it) Texen-1.0 shortly, which is a standalone
> version of the Texen tool on which the Torque generator is based. I
> know that you are in the process of releasing torque-3.3
Hi,
I'd like to warn you that we will release (we already voted, tagged,
rolled and deployed it) Texen-1.0 shortly, which is a standalone
version of the Texen tool on which the Torque generator is based. I
know that you are in the process of releasing torque-3.3 and I want to
urge you to base it n
Author: tv
Date: Tue May 1 03:46:05 2007
New Revision: 534001
URL: http://svn.apache.org/viewvc?view=rev&rev=534001
Log:
Added the call to BasePeer.correctBooleans() to LargeSelect.
Fixed the handling of unqualified column names in BasePeer.correctBooleans(),
Gracefully handle the case of a defau
LargeSelect is missing the correctBooleans() call. BasePeer.correctBooleans()
must handle defaultTableMap==null
---
Key: TORQUE-92
URL: https://issues.apac