From: | Vincent Fayolle <v(dot)fayolle(at)decision-network(dot)eu> |
---|---|
To: | "pgsql-odbc(at)postgresql(dot)org" <pgsql-odbc(at)postgresql(dot)org> |
Subject: | ODBC attribute not implemented ? |
Date: | 2021-07-01 21:54:23 |
Message-ID: | PR0P264MB1355914153A4EAC2194091E1AB009@PR0P264MB1355.FRAP264.PROD.OUTLOOK.COM |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-odbc |
Hello everyone,
I have an issue with a standard ODBC (1.0) attribute: SQL_ATTR_MAX_ROWS
When this attribute is set (it is a number), it must limit the number of rows returned by the query.
When I check the trace, I can see that the use seems OK, and sent to the driver (here I want to get the first 37 rows of a query) :
ODBC: ENTER SQLSetStmtAttr 362 1940794843 tkvercn1 0 DOSSCHT
0x0000000006be30c0 363 1940794843 tkvercn1 0 DOSSCHT
1 <SQL_ATTR_MAX_ROWS> 364 1940794843 tkvercn1 0 DOSSCHT
37 365 1940794843 tkvercn1 0 DOSSCHT
-6 <SQL_IS_INTEGER> 366 1940794843 tkvercn1 0 DOSSCHT
ODBC: EXIT SQLSetStmtAttr with return code 0 (SQL_SUCCESS) 367 1940794843 tkvercn1 0 DOSSCHT
But the query trace of postgre, we can see that this value ok 37 lines is not used to limit the query (I have a select *) :
2021-07-01 23:40:43.897 CEST [11396] LOG: exécute _PLAN000000000054FF00: SELECT * FROM TEST
I tried on windows and centos, with the last odbc driver (v13).
Can I add something in the odbc.ini or this attribute is not implemented ?
Thanks for you reply... and time !
Vincent
From | Date | Subject | |
---|---|---|---|
Next Message | fengzh.fnst@fujitsu.com | 2021-07-07 08:50:31 | SQLExecute returns empty SQLState and SQLMsg |
Previous Message | Justin Chin-You | 2021-06-17 09:48:49 | Re: Matching Driver Version + DB Engine Version |