[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference orarep::nomahs::odbc_rdb_driver

Title:	DEC ODBC Driver
Notice:	DEC ODBC Driver V2.0 Now Available
Moderator:	SQLSRV::MAVRIS

Created:	Tue Dec 29 1992
Last Modified:	Fri Jun 06 1997
Last Successful Update:	Fri Jun 06 1997
Number of topics:	1357
Total number of notes:	4864

1312.0. "Digit cut off when fetching negative real value using ODBC" by AVMSV1::EKREISLE (Erich Kreisler) Wed Mar 19 1997 07:45

Hello,

One of our customers found that when a real value is fetched using ODBC from Rdb
and this value is negative the last digit of the exponent gets stripped away.

Based on the information the customer sent to me the ODBC SDK 2.10 Appendix D
sepcifies a length of 13 for SQL_REAL (a sign, 7 digits, a decimal point, 
the letter E, a sign, and 2 digits) but our ODBC driver returns 8 digits and 
when the value is negative the last digit of the exponent is lost.

Here is an extract from a ODBC logfile

<BOUND>
        6
        SQL_C_CHAR
        [13]-8.3936000E-0 <--Error
        14
        16

I can provide a complete log if needed. 

Versions: Rdb 6.1-03
	  SQL/Services 6.1-01
	  ODBC 2.0.20/2.10.11

The problem happens only in MSQuery because it gets the data in chracters and 
not as reals.
Question: is this a known problem (did not find it here in notes or UK WWS) ?

Ciao,
	erich

T.R	Title	User	Personal Name	Date	Lines
1312.1	known prob	M5::JBALOGH		`Wed Mar 19 1997 08:32`	10
	Yes, this is a known problem with MS Query or any ODBC app that fetches REAL or DOUBLE data types into chars. The precision for an Rdb DOUBLE or REAL is more that the spec allows. The ODBC driver specifies 13 chars for REAL but Rdb is sending it 14 so the driver has to cut 1 off to meet the spec. Not much can be done except to get Microsoft to change the ODBC spec. John
1312.2		M5::JBALOGH		`Wed Mar 19 1997 08:33`	5
	One thing you may be able to do is to CAST the REAL to another data type such as integer or char. You could do this is in a query or in a view. John
1312.3		AVMSV1::EKREISLE	Erich Kreisler	`Wed Mar 19 1997 08:56`	11
	> The ODBC driver specifies 13 chars for REAL but Rdb is sending it 14 > so the driver has to cut 1 off to meet the spec. >Not much can be done except to get Microsoft to change the ODBC spec. So we do not conform to the ODBC spec in that area. My opinion is that this is our problem and not the problem of MS if we do not conform to ODBC Spec. On the other hand is this documented anywhere (Ichecked but did not find it). Any more information welcome, erich
1312.4		M5::JBALOGH		`Wed Mar 19 1997 10:24`	11
	The point was that we DO conform to the spec. The ODBC spec says we have to return 13 characters. The driver returns 13 characters. The problem is that Rdb carries a greater precision than the ODBC spec allows so something has to go. I really don't think Rdb engineering is going to reduce precision in Rdb to match the Microsoft spec. I guess the real question is going to be... What does SQL92 say about length of a real? John
1312.5	documented...	M5::JBALOGH		`Wed Mar 19 1997 15:19`	6
	BTW: This behavior is documented in the readme.txt file that ships with ODBC driver. John
1312.6		AVMSV1::EKREISLE	Erich Kreisler	`Fri Mar 21 1997 08:53`	7
	Re .-1 I hope the customer accepts what we have documented. I also recommended to use the workarounds described in that document. Ciao, erich
1312.7	Digit cut off when fetching negative real value using ODBC	ataxp1.at.oracle.com::RROEHRIC	Oracle Austria	`Mon Mar 24 1997 06:07`	6
	The customer doesn't accept the workaround, casting the real. In his opinion the odbc-driver should convert the real or truncate one precision-digits and not truncate the exponent. Regards Reinhold
1312.8	Bug 471042	148.87.13.1::EKREISLE	Erich Kreisler	`Fri Mar 28 1997 07:54`	0