tfischer    2005/05/08 09:19:31

  Modified:    src/generator/src/templates/om Peer.vm
               xdocs    changes.xml
  Log:
  In Torque 3.1.1, BIT columns were treated as Strings with the value 0 and 1. 
This caused problems in various DBs (e.g. HSQLDB).
  Reverted to the old behaviour: The adapter decides for selects which value is 
used, the db driver (via PreparedStatement.setValue()) decides for 
inserts/updates.
  
  Revision  Changes    Path
  1.15      +0 -10     db-torque/src/generator/src/templates/om/Peer.vm
  
  Index: Peer.vm
  ===================================================================
  RCS file: /home/cvs/db-torque/src/generator/src/templates/om/Peer.vm,v
  retrieving revision 1.14
  retrieving revision 1.15
  diff -u -r1.14 -r1.15
  --- Peer.vm   5 May 2005 10:44:42 -0000       1.14
  +++ Peer.vm   8 May 2005 16:19:31 -0000       1.15
  @@ -307,16 +307,6 @@
                   criteria.add($cup, ((Boolean) 
possibleBoolean).booleanValue() ? "Y" : "N");
               }
            }
  -    #elseif ($col.isBit())
  -        // check for conversion from boolean to bit (1/0)
  -        if (criteria.containsKey($cup))
  -        {
  -            Object possibleBoolean = criteria.get($cup);
  -            if (possibleBoolean instanceof Boolean)
  -            {
  -                criteria.add($cup, ((Boolean) 
possibleBoolean).booleanValue() ? "1" : "0");
  -            }
  -         }
       #end
     #end
       }
  
  
  
  1.157     +5 -0      db-torque/xdocs/changes.xml
  
  Index: changes.xml
  ===================================================================
  RCS file: /home/cvs/db-torque/xdocs/changes.xml,v
  retrieving revision 1.156
  retrieving revision 1.157
  diff -u -r1.156 -r1.157
  --- changes.xml       8 May 2005 16:14:07 -0000       1.156
  +++ changes.xml       8 May 2005 16:19:31 -0000       1.157
  @@ -29,6 +29,11 @@
   
     <release version="3.2-dev" date="in CVS">
       <action type="fix" dev="tfischer">
  +      In Torque 3.1.1, BIT columns were treated as Strings with the value 0 
and 1.
  +      This caused problems in various DBs (e.g. HSQLDB). Reverted to the old 
behaviour:
  +      The adapter decides for selects, the db driver for inserts/updates.
  +    </action> 
  +    <action type="fix" dev="tfischer">
         For inserting/updating tables with BIT columns, use booleans instead 
of 
         integers for the prepared statement used to update/insert BIT columns
       </action> 
  
  
  

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to