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 tf...@apache.org on 2005/04/22 07:31:04 UTC

cvs commit: db-torque/xdocs oracle-howto.xml

tfischer    2005/04/21 22:31:04

  Modified:    xdocs    oracle-howto.xml
  Log:
  Added documentation for the usage of the types DATE, TIME and TIMESTAMP
  See issue TRQS263 in Scarab
  
  Revision  Changes    Path
  1.5       +56 -10    db-torque/xdocs/oracle-howto.xml
  
  Index: oracle-howto.xml
  ===================================================================
  RCS file: /home/cvs/db-torque/xdocs/oracle-howto.xml,v
  retrieving revision 1.4
  retrieving revision 1.5
  diff -u -r1.4 -r1.5
  --- oracle-howto.xml	19 Aug 2004 02:24:49 -0000	1.4
  +++ oracle-howto.xml	22 Apr 2005 05:31:04 -0000	1.5
  @@ -8,25 +8,71 @@
   
   <body>
   
  -<section name="Introductory note">
  +  <section name="Oracle Howto" >
  +
  +    <p>
  +      Saravana Kannan is maintaining a patched version of Village that 
  +      supports Oracle LOBs: 
  +      <a href="https://sweb.uky.edu/~skkann2/village/index.html">Village 2.0 
  +      Patched for Oracle LOBs - For use with Torque 3.1</a>
  +    </p>
  +    
  +    <p>
  +      The data type TIME only has day accuracy for Oracle. This is due to the 
  +      underlying village library and the fact that oracle does not support 
  +      a SQL type TIME.
  +      If you are using Oracle 9i and later, you can use the type TIMESTAMP
  +      instead which gives you millisecond accuracy.
  +    </p>
  +    
  +    <subsection name="Oracle versions">
  +      <p>
  +        This version of Torque is optimized for Oracle 9i and later. 
  +        The following issues exist for older versions of Oracle:
  +      </p>
  +     
  +      <p>
  +        The data type TIMESTAMP is not supported up to and including
  +        Oracle 8.1.7. Either use the types DATE or TIME instead of TIMESTAMP 
  +        or change the following line in the class 
  +        org.apache.torque.engine.platform.PlatformOracleImpl 
  +        in the generator source
  +      </p>
  +
  +      <source>
  +setSchemaDomainMapping(new Domain(SchemaType.TIMESTAMP, "TIMESTAMP"));</source>
  +
  +      <p>
  +        to
  +      </p>
  +      
  +      <source>
  +setSchemaDomainMapping(new Domain(SchemaType.TIMESTAMP, "DATE"));</source>
  +
  +      <p>
  +        and rebuild the generator from source.
  +        However, both possibilities will give you only day accuracy for the
  +        data types DATE, TIME and TIMESTAMP
  +      </p>
  +      
  +    </subsection>
  +
  +  </section>
  +
  +
  +<section name="Introductory note for the following sections">
   
   <p>
  -This HOWTO was written some time ago and was targeted at Oracle 8i and the
  -version of Torque that was coupled with the 
  +The following part of this HOWTO was written some time ago and was 
  +targeted at Oracle 8i and the version of Torque that was coupled with the 
   <a href="http://jakarta.apache.org/turbine/">Turbine</a> application framework.
   Contributions towards updating the information below can be submitted to the 
   <a href="mailto:torque-dev@db.apache.org">Torque Dev mailing list</a>.
   </p>
   
  -<p>
  -Saravana Kannan is maintaining a patched version of Village that supports Oracle 
  -LOBs: <a href="https://sweb.uky.edu/~skkann2/village/index.html">Village 2.0 
  -Patched for Oracle LOBs - For use with Torque 3.1</a>
  -</p>
  -
   </section>
   
  -<section name="Oracle Howto">
  +<section name="Oracle Howto for Turbine">
   
   <p>
   This HOWTO aims to be a simple guide to make Turbine run with an existing
  
  
  

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