I'm sending the two statements in one single pass-through query. Both statements are separated by a semicolon. I even tried to remove the carridge return at the end of the first statement, but of course, it has no effect.
Postgres handles the sql commands fine. But I'm not able to get the return value from "func_test_insert", as soon as I add an sql command BEFORE the function call. BUT, if I add this SQL command AFTER the function call, it's OK. Apparently, the first statement is considered to be the one that returns data. All others are executed, but their return value is discarded. I guess this is an Access issue, more than an ODBC one, right?
De : Jeff Eckermann [mailto:jeff_eckermann(at)yahoo(dot)com]
Envoyé : jeudi, 6. novembre 2003 16:35
À : Philippe Lang; pgsql-odbc(at)postgresql(dot)org
Objet : Re: [ODBC] Access, pass-through queries and isolation level
> Now if I want to change the isolation level before:
> set transaction isolation level serializable;
> select * from public."func_test_insert"();
> ... I cannot get the inserted id back in Access,
> from the pass-through query. Apprently, since the
> first query does not return any row, Access
> considers the whole query does not return anything.
Are you sending the two statements as separate queries
in your code? If so, try sending both as a single
query, i.e. one string, with a semicolon separating
the two. Access doesn't know you are sending two
statements in one, and Postgres will handle them just fine.
pgsql-odbc by date
|Next:||From: TANIDA Yutaka||Date: 2003-11-07 08:45:25|
|Subject: Bug in SQLColumns() and SQLTables() with "Parse Statement".|
|Previous:||From: Johann Zuschlag||Date: 2003-11-06 22:50:10|
|Subject: Re: ODBC|