Skip to Main Content

Java Database Connectivity (JDBC)

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Odd behaviors of Sybase ASA8.0

843854Jun 26 2003 — edited Jul 2 2003
I've just downloaded a trial version of ASA8.0....

According to the user's manual, when a table is created, the default for each field is NULL(able) unless NOT NULL is used. But after having created the table, every single field in my table shows up as NOT NULL regardless of whether or not the field was created with NOT NULL.

That I can live with..... but what's really strange is that if I accessed the newly created table with
com.sybase.jdbc2.jdbc.SybDriver, isReadOnly method reports that every single field is READ-ONLY whereas if I accessed it with sun.jdbc.odbc.JdbcOdbcDriver, everything is fine.
So my question is: is there another way I can tell if a field is really READ-ONLY (I've tried isWritable and isDefinitelyWritable methods with same results)?

Here are some additional info:

----------------------------
Product : Adaptive Server Anywhere, Version : 8.0.2.4122
Driver : jConnect (TM) for JDBC (TM), Version : jConnect (TM) for JDBC(TM)/5.5(Build 25051)/P/EBF9689/JDK12/Fri Aug 10 12:35:48 2001

Every field is reported as READ-ONLY

----------------------------
Product : Adaptive Server Anywhere, Version : 08.00.0000
Driver : JDBC-ODBC Bridge (DBODBC8.DLL), Version : 2.0001 (08.00.0002)

no READ-ONLY

----------------------------

Any help would be appreciated.



;o)

V.V.

PS: I've just noticed that the reported version numbers are not the same (I've no idea why).
Comments
Locked Post
New comments cannot be posted to this locked post.
Post Details
Locked on Jul 30 2003
Added on Jun 26 2003
10 comments
168 views