Skip site navigation (1) Skip section navigation (2)

Re: SQLSetPos problem ?

From: Hiroshi Inoue <inoue(at)tpf(dot)co(dot)jp>
To: "lothar(dot)behrens(at)lollisoft(dot)de" <lothar(dot)behrens(at)lollisoft(dot)de>
Cc: pgsql-odbc(at)postgresql(dot)org
Subject: Re: SQLSetPos problem ?
Date: 2006-12-13 00:50:11
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-odbc
lothar(dot)behrens(at)lollisoft(dot)de wrote:
> Hiroshi Inoue schrieb:
>> lothar(dot)behrens(at)lollisoft(dot)de wrote:
>>> Hiroshi Inoue schrieb:
>>>> lothar(dot)behrens(at)lollisoft(dot)de wrote:
>>>>> Hi,
>>>>> I am using unixodbc in the latest version and psqlodbc 07.03.0200.
>>>>> Having many queries working
>>>>> good in my application one gives me this error, when updating a row.
>>>> The version 7.3.0200 is pretty old.
>>>> Please try the 8.2.xxxx version.
>>> I need cursor functionality like first,back,next,last. Does the latest
>>> driver support it ?
>> Yes at least on Windows.
> Currently I have figured out, that my SQL_ADD statement fails
> (SQLSetPos).
> It seems, that I cannot insert new rows, because of foreign key
> constraints.
> Removing the NOT NULL clauses of that columns didn't helped.
> With PGAdmin I was able to test inserting such a row. That worked.
> Any ideas ?

How do you setting the foreign key column using PGadmin ?

> If the bound columns having the wrong value - such as a non exsisting
> foreign key -
> how must it be filled to indicate a NULL value ?
> I bind such a column that way:
> buffer = malloc((ColumnSize+1)*rows);
> memset(buffer, 0, (ColumnSize+1)*rows);
> ret = SQLBindCol(hstmt, column, SQL_C_CHAR, buffer, (ColumnSize+1),
> &cbBufferLength);
> Is that wrong ?

I'm afraid I'm misunderstanding your point.
Please set SQL_NULL_DATA to cbBufferLength to indicate the column is NULL.
Also set SQL_COLUMN_IGNORE to cbBufferLength to ignore the column.

Hiroshi Inoue

In response to


pgsql-odbc by date

Next:From: noreplyDate: 2006-12-13 02:06:05
Subject: [ psqlodbc-Bugs-1000738 ] Wrong ODBC state (42P01 or 42P07) is returned on dropping/creating table
Previous:From: Caio BegottiDate: 2006-12-13 00:03:05
Subject: Re: possible odbc driver bug with postgresql-7.4

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group