You are viewing a plain text version of this content. The canonical link for it is here.
Posted to torque-dev@db.apache.org by "Thomas Vandahl (JIRA)" <ji...@apache.org> on 2007/05/01 12:41:15 UTC
[jira] Created: (TORQUE-92) LargeSelect is missing the
correctBooleans() call. BasePeer.correctBooleans() must handle
defaultTableMap==null
LargeSelect is missing the correctBooleans() call. BasePeer.correctBooleans() must handle defaultTableMap==null
---------------------------------------------------------------------------------------------------------------
Key: TORQUE-92
URL: https://issues.apache.org/jira/browse/TORQUE-92
Project: Torque
Issue Type: Bug
Components: Runtime
Affects Versions: 3.3-RC2
Environment: PostgreSQL
Reporter: Thomas Vandahl
Assigned To: Thomas Vandahl
Fix For: 3.3-RC3
When using LargeSelect with PostgreSQL, the handling of boolean values in the Criteria fails for BOOLEANINT and BOOLEANCHAR values because the call to correctBooleans() is missing.
To use this, the call of BasePeer.correctBooleans(criteria, tableMap) must gracefully handle the case of tablemap == null, because we don't have access to a decent tableMap.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: torque-dev-unsubscribe@db.apache.org
For additional commands, e-mail: torque-dev-help@db.apache.org
[jira] Resolved: (TORQUE-92) LargeSelect is missing the
correctBooleans() call. BasePeer.correctBooleans() must handle
defaultTableMap==null
Posted by "Thomas Vandahl (JIRA)" <ji...@apache.org>.
[ 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 handling of unqualified column names in BasePeer.correctBooleans(),
Gracefully handle the case of a defaultTableMap==null,
Added testCases to verify the behaviour.
> LargeSelect is missing the correctBooleans() call. BasePeer.correctBooleans() must handle defaultTableMap==null
> ---------------------------------------------------------------------------------------------------------------
>
> Key: TORQUE-92
> URL: https://issues.apache.org/jira/browse/TORQUE-92
> Project: Torque
> Issue Type: Bug
> Components: Runtime
> Affects Versions: 3.3-RC2
> Environment: PostgreSQL
> Reporter: Thomas Vandahl
> Assigned To: Thomas Vandahl
> Fix For: 3.3-RC3
>
>
> When using LargeSelect with PostgreSQL, the handling of boolean values in the Criteria fails for BOOLEANINT and BOOLEANCHAR values because the call to correctBooleans() is missing.
> To use this, the call of BasePeer.correctBooleans(criteria, tableMap) must gracefully handle the case of tablemap == null, because we don't have access to a decent tableMap.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: torque-dev-unsubscribe@db.apache.org
For additional commands, e-mail: torque-dev-help@db.apache.org