ODBC isolationi level SQL_TXN_SERIALIZABLE -> "08001 Already connected."

From: Hong06 <honghe06(at)gmail(dot)com>
To: pgsql-odbc(at)postgresql(dot)org
Subject: ODBC isolationi level SQL_TXN_SERIALIZABLE -> "08001 Already connected."
Date: 2016-09-30 13:41:26
Message-ID: 1475242886765-5923778.post@n3.nabble.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-odbc

Hello everyone,

I just ran into following issue with a big surprise that it does not work in
ODBC.

What I am doing is:
- set the isolation level to: SQL_TXN_SERIALIZABLE
- then connect to postgres database via ODBC function SQLDriverConnect()

Example code:

ret = SQLSetConnectAttr(hDbc, SQL_ATTR_TXN_ISOLATION,
(SQLPOINTER)SQL_TXN_SERIALIZABLE, SQL_IS_INTEGER);

ret = SQLDriverConnect(hConnect,
0,
(SQLCHAR*)connString,
ustrlen((unsigned char *)connString),
NULL,
0,
NULL,
SQL_DRIVER_NOPROMPT);

Then SQLDriverConnect() returns -1 with error code: "08001 Already
connected."

With other isolation level like SQL_TXN_READ_COMMITTED, it works fine.

Any idea to solve this problem? Or is this a Postgres ODBC bug? I couldn't
find anything here or on Google.

--
View this message in context: http://postgresql.nabble.com/ODBC-isolationi-level-SQL-TXN-SERIALIZABLE-08001-Already-connected-tp5923778.html
Sent from the PostgreSQL - odbc mailing list archive at Nabble.com.

Responses

Browse pgsql-odbc by date

  From Date Subject
Next Message Tsunakawa, Takayuki 2016-10-03 03:19:48 Re: ODBC isolationi level SQL_TXN_SERIALIZABLE -> "08001 Already connected."
Previous Message Adrian Klaver 2016-09-28 19:40:45 Re: psqlodbc without libpq