#17 date and large file support for Oracle 9i Part 1

open
nobody
None
5
2004-03-23
2004-03-23
Satfreak
No

The supplied oracle schema has some drawbacks in oracle 9i:

1. the time section of a datetime field is always set
to 00:00

2. large object support does not work.

Fix:

1. Use "timestamp" datatype instead of "DATE" fields.

2. Use "LONG" datatype instead of "CLOB" and overwrite
the track+ village-2.0-dev-20030825.jar archive with
the "village.jar" inside the attached jar archive.

ALTERNATIVELY: get a current village source-release and
exchange the file "Value.java" recompile it, create an
archive and overwrite "village-2.0-dev-20030825.jar"
in your tomcat folder.

For new schames use the "track-schema.sql" inside the
jar archive.

Discussion

  • Satfreak
    Satfreak
    2004-03-23

    3 Files. See detailed description

     
  • Logged In: YES
    user_id=364010

    Does the changed village.jar work with other databases as
    well? I had some problems with Firebird after a previous
    change.

     
  • Satfreak
    Satfreak
    2004-04-16

    Logged In: YES
    user_id=972460

    The changes were not tested against other databases. The
    change I made was the following: Supply java code for
    accessing large datatypes using Input and Output streams. I
    think this should be the correct behaviour for all
    databases. However if a database does not support streamed
    Input/Output this fix can cause problemens. However, in this
    case the database should not tag the column as "large" (with
    SQL Konstants), because there is no other way of accessing
    such columns, at least no method I can think of.