db-torque-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From tfisc...@apache.org
Subject cvs commit: db-torque/xdocs changes.xml
Date Tue, 17 May 2005 07:07:22 GMT
tfischer    2005/05/17 00:07:22

  Modified:    xdocs    changes.xml
  Log:
  Inserted a note that BIT is not longer supported for Oracle
  
  Revision  Changes    Path
  1.158     +6 -1      db-torque/xdocs/changes.xml
  
  Index: changes.xml
  ===================================================================
  RCS file: /home/cvs/db-torque/xdocs/changes.xml,v
  retrieving revision 1.157
  retrieving revision 1.158
  diff -u -r1.157 -r1.158
  --- changes.xml	8 May 2005 16:19:31 -0000	1.157
  +++ changes.xml	17 May 2005 07:07:22 -0000	1.158
  @@ -30,8 +30,13 @@
     <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:
  +      This caused problems in various DBs which natively support BOOLEAN columns
  +      but do not support implicit String conversion.(e.g. HSQLDB).
  +      Reverted to the old behaviour:
         The adapter decides for selects, the db driver for inserts/updates.
  +      However, this behavior breaks BIT support for Databases which do not have
  +      a native boolean datatype (like Oracle). For these Databases, use BOOLEANINT
  +      (or BOOLEANCHAR) column types for Booleans.
       </action> 
       <action type="fix" dev="tfischer">
         For inserting/updating tables with BIT columns, use booleans instead of 
  
  
  

---------------------------------------------------------------------
To unsubscribe, e-mail: torque-dev-unsubscribe@db.apache.org
For additional commands, e-mail: torque-dev-help@db.apache.org


Mime
View raw message