[TORQUE-92] LargeSelect is missing the correctBooleans() call. BasePeer.correctBooleans() must handle defaultTableMap==null

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.3-RC2
• Fix Version/s: 3.3-RC3
• Component/s: Runtime
• Environment: PostgreSQL
• Assignee: Thomas Vandahl
• Reporter: Thomas Vandahl
• Created: 01/May/07 10:39
• Updated: 27/Sep/12 19:38
• Resolved: 01/May/07 11:25

Description

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.