Re: What is best JDBC driver for Informix
Posted in 1998
Hi Allan, sorry for this public conversation, somehow my mail keeps coming back,... so it is a public discussion :] at http://www5.sco.com/Support/assist/bug.html I entered the bug. The bugid given to me is 2841. This was handed out by http://www5.sco.com/cgi-bin/bug.cgi You need my e-mail address to check the bug status, maybe you have other access though, you might use it :) the date was 02.04.1998 12:28 ++++++++++++++++++++++++++++++++++++++++++++++++++++++ Bug Status Report Your bugid is: 2841 Receipt of your submitted bug is acknowledged. Check at a later time for additional status. Click here to see the original bug report ++++++++++++++++++++++++++++++++++++++++++++++ Submitted by: Kemal Soysal Bug Id: 2841 Submited on: ----------- DATE: 04/02/98 TIME: 01:51:08 Customer Information -------------------- Customer Name: Kemal Soysal Company: Soysal Systems Location: UK Email Address: Kemal@staps.de Phone Number: +49(30)42161607 Fax Number: +49(30)42161608 Product Information ------------------- Product: Vision97 sqlrjdbc Division: Other Version and Release: 4.15.15 Hardware Information -------------------- Machine: RAM: 64 MB Video Card: Hard Drive Controller: Hard Drive: Network Adaptor: Other: Problem Description ------------------- Software or Documentation: Software Area (Component or Book): Software Component Brief Description: Informix Date Datetime in sql.Types Detailed Description: the jdbc driver returns in the MetaData the wrong type number!!!! java.sql.Types has only Date, Time & Timestamp finals which are 91, 92, 93 the jdbcdriver returns 9 for any type of the above Kemal Soysal end report ------------------------------------------------------------------ The problem is, that whoever wrote the type conversion must have got sick of the class java.sql.Types including 3 different date-formats, literally : public final static int DATE = 91; public final static int TIME = 92; public final static int TIMESTAMP = 93; It is all one type: 9. After the first exception of non-existing data type in our application we wrote a work around: we do not ask for date types any more... we ask for a string compound from SQL-functions SELECT YEAR( <datefield> ) || "-" || MONTH( <datefield> ) || "-" || DAY( <datefield> ) date FROM <table> ORDER BY date That this is not portable did not bother us, because we knew, that some day SCO would fix the bug, because we reported it. I wonder, how pure Java check did not "see" this problem, but I think it is hard to find out anyway! Allan Gould wrote: > Kemal Soysal wrote: > > > Allan Gould wrote: > > > > > You could try our JDBC/ODBC driver: SCO SQL-Retriever. Take a look at > > > http://www.sco.com/vision/products/sqlretriever/ for more information and > > > a downloadable eval. > > > > But be carefull,... it is not fully java compatible with informix !!!! > > I reported a bug with the version 5 of informix database OnLine,... > > I think it is still persisting. Or you take the ones from Informix, > > "they should be ok!" (I've been told) > > Perhaps you could clarify as I am not sure what you refer to, nor can I find a > reference to yourself on our call logging system having reported a problem. If > you would care to contact me, perhaps we could further this matter. > > Regards > > Allan Gould > SQL-Retriever Technical Support > allang@sco.com -- Kemal Soysal - Solmsstrasse 33 - 10961 Berlin Kemal@staps.de ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ "Could I disassemble the .class into .java with JDK, so I can edit it?" "Try ANTLR"