3.17. Sybase Adaptive Server

3.17.1. Known issues with Sybase

Example 3.18. Example properties for Sybase

kodo.ConnectionDriverName: com.sybase.jdbc3.jdbc.SybDriver
kodo.ConnectionURL: \
    jdbc:sybase:Tds:SERVER_NAME:4100/DB_NAME?ServiceName=DB_NAME&BE_AS_JDBC_COMPLIANT_AS_POSSIBLE=true

3.17.1. Known issues with Sybase

  • The "DYNAMIC_PREPARE" parameter of the Sybase JDBC driver cannot be used with Kodo.

  • Datastore locking cannot be used when manipulating many-to-many relations using the default Kodo schema created by the schematool, unless an auto-increment primary key field is manually added to the table.

  • Persisting a zero-length string results in a string with a single space characted being returned from Sybase, Inc.'s JDBC driver.

  • The BE_AS_JDBC_COMPLIANT_AS_POSSIBLE is required in order to use datastore (pessimistic) locking. Failure to set this property may lead to obscure errors like "FOR UPDATE can not be used in a SELECT which is not part of the declaration of a cursor or which is not inside a stored procedure.".

 

Skip navigation bar   Back to Top