BUG #7891: ODBC error on SQL_REAL
От | alain.reymond@ceia.com |
---|---|
Тема | BUG #7891: ODBC error on SQL_REAL |
Дата | |
Msg-id | E1U7r6C-0002Zn-R0@wrigleys.postgresql.org обсуждение исходный текст |
Список | pgsql-bugs |
The following bug has been logged on the website: Bug reference: 7891 Logged by: Alain Reymond Email address: alain.reymond@ceia.com PostgreSQL version: 9.2.3 Operating system: Centos 5.9 (32 bits) Description: = Hello, I use Postgresql 9.2.3 under Centos 5.9. (32 bits). We access our database through unixodbc (unixODBC-2.2.11-10.el5.i386). I have defined a table CREATE TABLE rresultats ( numbil integer, numparam smallint, mesure smallint, dev real ) I access the table via esql for cobol. When I try to insert a record in the table, I get a sqlcode =3D -7 in retur= n. It seems that SQL_REAL is not properly mapped to the comp-1 in cobol ( =3D float in C). Here is the logfile : [ODBC][19186][SQLBindParameter.c][193] Entry: = Statement =3D 0x83227c8 = Param Number =3D 4 = Param Type =3D 1 = C Type =3D 7 SQL_C_FLOAT = SQL Type =3D 7 SQL_REAL = Col Def =3D 7 = Scale =3D 0 = Rgb Value =3D 0x83225a8 = Value Max =3D 4 = StrLen Or Ind =3D 0x83225a4 [ODBC][19186][SQLBindParameter.c][339] Exit:[SQL_SUCCESS] [ODBC][19186][SQLExecute.c][183] Entry: = Statement =3D 0x83227c8 [ODBC][19186][SQLExecute.c][344] Exit:[SQL_ERROR] DIAG [S1000] ERREUR: syntaxe en entr=C3=83=C2=A9e invalide pour le= type real : =C3=82=C2=AB 15,5 =C3=82=C2=BB au caract=C3=83=C2=A8re 141; Error while executing the query [ODBC][19186][SQLError.c][342] Entry: = Statement =3D 0x83227c8 = SQLState =3D 0x82e434a = Native =3D 0xbfa1e540 = Message Text =3D 0x82e4350 = Buffer Length =3D 1023 = Text Len Ptr =3D 0xbfa1e546 [ODBC][19186][SQLError.c][379] Exit:[SQL_SUCCESS] = SQLState =3D S1000 = Native =3D 0xbfa1e540 -> 7 = Message Text =3D [[unixODBC]ERREUR: syntaxe en entr=C3=83=C2= =A9e invalide pour le type real : =C3=82=C2=AB 15,5 =C3=82=C2=BB au caract=C3=83= =C2=A8re 141; Error while executing the query] I tried with double precision : same thing. Curiously, we have a version using unixODBC-2.2.11-7.1 and Posgresql 8.4 and have no problem... Regards
В списке pgsql-bugs по дате отправления: