R: [Firebird-odbc-devel] bug in resolving Timestamp, problem in NUMERIC format

[Ferrari A. <fer...@ds...>]

Thanks for the response,
I'm using interclient too, without problems up to now, also for Numeric =
fields. I think because i don't use store procedures.
To compile ODBC-JDBC i used Microsoft Visual C++ easily, if you have =
this product and you want compile the source, you must download the cvs =
files, (If you can't i'll send them to you) the SDK for =
Interbase/Firebird and setting properly the Linking and C++ properties.
Currently i leaved ODBC-JDBC driver and i'm looking at =
http://ofbodbc.sourceforge.net/=20
It is another open source driver, and for my need it seems working fine.
=20
Best Regards,
Alberto Ferrari

-----Messaggio originale-----
Da: Siavcom Software S. de R.L. de C.V. [mailto:si...@ax...]
Inviato: luned=EC 29 aprile 2002 22.35
A: Ferrari Alberto; fir...@li...
Oggetto: Re: [Firebird-odbc-devel] bug in resolving Timestamp, problem =
in NUMERIC format


Recently I have working with JDBC and the last version (2.1) of =
Interclient for Firebird. I found some errors using Numeric and Decimal =
Fields=20
In java with JDBC and Interclient when a select or store procedure =
return a Decimal or Numerical Field with one or more decimal Interclient =
return the next error=20
=20
Error: [interclient] Unsupported feature: Using a JDBC 2 method which is =
not yet supported.
See API reference for exception =
interbase.interbclient.DriverNotCaptableException
[SQLCode: 7], [SQLState: 0A000]
=20
The Firebird-odbc JDBC I undertand use JDBC, I almost sure that many =
problem using Numeric or Decimals Fields come from JDBC
The solution is to chage all fields numeric or decimal to float or =
doubble precision but There are one problem more :
                       When you use a Float o double precision Field, =
JDBC lost decimasl. Maximun you can use 3 precision decimals if you need =
more precision
                       Is not the answer.
=20
=20
I readed many mail where many people found bugs in ODBC-JDBC but this =
Bugs an solutions never had been updated in CVS tree.
=20
If Firebird is not interested in update the new bug fixed I=B4m propose =
create a new Open Source ODBC-JDBC in sourceforce with other name, where =
the community can development and upgrade the new changes=20
=20
Who can help me how can I dowload the ODBC-JDBC and make exe file.
=20
=20
I=B4m developer software. I=B4m using Visual FoxPro and firebid. I use =
Easy Soft ODBC but I found that Easy Soft ODBC use the client of =
Interbase.
The client of Interbase use a lot of trasmision ( all data schema are =
trasmited on each  table or store procedure are consulted ) this cause a =
lot of trafic over the Net. If the client is in a LAN (Local Area =
Network) is not a big problem but if the client is outside of the LAN ( =
using Interent, DS0 ect) the connexion is slow.
=20
I made test using ODBC-JDBC in the past but when I tried to make a =
connection I had a fatal error an my aplication is closed.
=20
I Belive using ODBC-JDBC is the best solution of ODBC but we need the =
colaboration of all yours in making test and found and fix bugs.
=20
=20
=20
Thanks
=20
Eng. Fernando Cuadras
General Manager Siavcom Software=20
www.siavcom.com.mx
si...@ax...
=20
=20
=20
=20
=20
=20
=20
=20
=20
=20
=20
=20
=20

=20
----- Original Message -----=20
From: Ferrari  <mailto:fer...@ds...> Alberto=20
To: fir...@li...=20
Sent: Monday, April 29, 2002 2:22 AM
Subject: [Firebird-odbc-devel] bug in resolving Timestamp, problem in =
NUMERIC format


I all,

I don't know if there is a bug in resolving Timestamp, but I have an =
exception when i try to get a column of this type

I looked the code,  and i have found that if i comment these lines

if ((days > 24855) || (days < -24885))
                    throw SQLEXCEPTION (CONVERSION_ERROR, "date out of =
range");
at IscStatement::setValue(Value *value, XSQLVAR *var)

the driver works, but I have some problem in TIME format (the resulted =
format is not corrected in TIMESTAMP and in TIME).

I have a problem also for NUMERIC, it seems that the resulted metada is =
not correct, it seems to be a Integer not a Numeric.

Any suggestion??

Best regards,
Alberto Ferrari


_______________________________________________
Firebird-odbc-devel mailing list
Fir...@li...
https://lists.sourceforge.net/lists/listinfo/firebird-odbc-devel