Re: Cursor for a positioned update: "cursor <name> does not exist" error

From: Hiroshi Inoue <inoue(at)tpf(dot)co(dot)jp>
To: Sam Varshavchik <mrsam(at)courier-mta(dot)com>
Cc: pgsql-odbc(at)postgresql(dot)org
Subject: Re: Cursor for a positioned update: "cursor <name> does not exist" error
Date: 2013-05-23 13:20:07
Message-ID: 519E1787.1070903@tpf.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-odbc

Hi Sam,

(2013/05/23 7:11), Sam Varshavchik wrote:
> I'm using postgresql-odbc-09.01.0200 with postgresl-9.2.4
>
> According to the documention for SQLSetCursorName
> (http://msdn.microsoft.com/en-us/library/windows/desktop/ms711707%28v=vs.85%29.aspx)
>
> I don't really need to use it, and ODBC will use a default name.
>
> With unixODBC and a Postgresql connection handle, SQLGetInfo() shows
> SQL_CA1_POS_UPDATE capability for SQL_STATIC_CURSOR_ATTRIBUTES1, and
> SQL_KEYSET_CURSOR_ATTRIBUTES1.

SQL_CA1_POS_UPDATE stands for thr capability about SQLSetPos function
not about positioned update.
Maybe we had better not support SQLSetCursorName to avoid the confusion.

regards,
Hiroshi Inoue

In response to

Browse pgsql-odbc by date

  From Date Subject
Next Message Joe Conway 2013-05-23 18:00:26 Re: ODBC does not handle WITH clause
Previous Message Hiroshi Inoue 2013-05-23 13:15:27 Re: ODBC does not handle WITH clause