Skip to Content.
Sympa Menu

freetds - [JDBC PATCH] updated README and KNOWN_BUGS to the best of my knowledge

freetds AT lists.ibiblio.org

Subject: FreeTDS Development Group

List archive

Chronological Thread  
  • From: Stefan Bodewig <bodewig AT bost.de>
  • To: <freetds AT franklin.oit.unc.edu>
  • Cc: freetds-jdbc-bugs AT internetcds.com
  • Subject: [JDBC PATCH] updated README and KNOWN_BUGS to the best of my knowledge
  • Date: 08 Sep 2000 15:54:56 +0200

Hi,

just a simple documentation update (most notable added a hint to
;tds=7.0). As for the KNOWN_BUGS stuff, there are two places where I'm
not sure whether the bug is fixed (t0021 and t0032 pass for me).

Finally I think the driver now supports decimals with more than 64
bits, but I'm not sure.

Stefan

Index: README
===================================================================
RCS file: /Repository/freetds_jdbc/README,v
retrieving revision 1.38
diff -u -r1.38 README
--- README	2000/08/11 18:15:49	1.38
+++ README	2000/09/08 13:41:50
@@ -46,7 +46,12 @@
 SQLServer and port 7100 for Sybase.  Generally you will need to
 specify the port number for Sybase, but not for SQLServer.
 
+If you want to enable support for some SQL Server 7.0 features (namely
+NCHAR types and CHAR/BYTE types with more than 255 bytes of length)
+you need to append ;tds=7.0 to your URL like in
 
+   jdbc:freetds:sqlserver://servername:port/database;tds=7.0
+
                                JDBC 2.0
 
 The driver can be compiled for JDBC version 2.0.  You will need to
@@ -99,7 +104,7 @@
                                 Status
 
 
-Status summary as of January 10, 2000
+Status summary as of September 8, 2000
 
    *  The driver now compiles and runs with either JDBC 1.0 or 2.0.
       There is a variable in the Makefile to choose which driver 
@@ -114,7 +119,7 @@
       work.
 
    *  The Connection class is mostly implemented.  Code dealing with 
-      catalogs, and the warning chain is not implemented.
+      catalogs is not implemented.
  
    *  The DatabaseMetaData class still has ~60 methods not implemented.
       I still haven't implemented enough methods to run most visual 
@@ -123,14 +128,13 @@
    *  The Driver class is fully functional.
 
    *  The PreparedStatement class does not have all the data types
-      implemented yet.  The warning chain code is not implemented.
+      implemented yet.
       setBytes() is implemented for IMAGE data.  This should give
       some support for people that need BLOBS.
  
    *  The ResultSet does not have all the getXXX() methods implemented
       yet.  getObject() is implemented for all SQLServer datatypes.
-      cursors are not implemented.  The warning chain is not implemented
-      yet.
+      cursors are not implemented.
  
    *  The ResultSetMetaData class currently implements only-
         isNullable()
@@ -147,7 +151,7 @@
         isSearchable()
    
    *  The Statement class is mostly implemented.  It is missing
-      cursor support and the warning chain code.  
+      cursor support.  
 
 Query timeouts and the cancel() method are working for SQLServer but
 not for Sybase.
Index: KNOWN_BUGS
===================================================================
RCS file: /Repository/freetds_jdbc/KNOWN_BUGS,v
retrieving revision 1.41
diff -u -r1.41 KNOWN_BUGS
--- KNOWN_BUGS	2000/08/11 18:15:49	1.41
+++ KNOWN_BUGS	2000/09/08 13:41:51
@@ -1,4 +1,4 @@
-Last updated August 1,  2000.
+Last updated September 8,  2000.
 
 
 Please send bug reports to freetds-jdbc-bugs AT internetcds.com
@@ -39,7 +39,8 @@
 names I'm not sure what to do with this problem.
 
 Doesn't handle TDS_DONEINPROC packets correctly.  Demonstrated by
-t0032.java.
+t0032.java. -- Passes, at least on SQL Server 7 (with tds=4.2 and
+7.0).
 
 Race condition between TdsComm.peek() and TdsComm.getByte().  Methods
 in TdsComm that access the inBuffer and inBufferIndex need to be
@@ -61,13 +62,11 @@
 time the driver should not be considered thread safe.  This shouldn't
 be too difficult to fix.
 
-PreparedStatement.setString() method fails if the string is more than
-255 characters long.  Demonstrated by t0021.java
-
 PreparedStatement.setBytes() fails if the destination column is
 BINARY.  The stored procedure that is created should have a formal
 parameter of type VARBINARY if the length of the byte array is < 256.
-Demonstrated by t0021.java
+Demonstrated by t0021.java -- Again, passes, at least on SQL Server 7
+(with tds=4.2 and 7.0).
 
 Doesn't handle 'compute' clauses yet.  Demonstrated by t0026.java
 
Index: unittests/t0021.java
===================================================================
RCS file: /Repository/freetds_jdbc/unittests/t0021.java,v
retrieving revision 1.6
diff -u -r1.6 t0021.java
--- t0021.java	1999/02/24 02:53:58	1.6
+++ t0021.java	2000/09/08 13:41:51
@@ -192,8 +192,8 @@
       insert.setBytes(1, smallarray);
       insert.setBytes(2, array1);
       insert.setBytes(3, array1);
-      insert.setString(4, "abcd" /* bigtext1 */);
-      insert.setString(5, "defg" /* bigtext1 */);
+      insert.setString(4, bigtext1);
+      insert.setString(5, bigtext1);
      
       count = insert.executeUpdate();
        


  • [JDBC PATCH] updated README and KNOWN_BUGS to the best of my knowledge, Stefan Bodewig, 09/08/2000

Archive powered by MHonArc 2.6.24.

Top of Page