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

Re: Still SQLSetPos problem even with minimal sample, SQL_NULL_DATA

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: Still SQLSetPos problem even with minimal sample, SQL_NULL_DATA
Date: 2006-12-18 23:40:30
Message-ID: 458726EE.6040906@tpf.co.jp (view raw or flat)
Thread:
Lists: pgsql-odbc
lothar(dot)behrens(at)lollisoft(dot)de wrote:
> Hi,
> 
> I have implemented setting SQL_COLUMN_IGNORE, SQL_NULL_DATA and have
> added functions
> to indicate this state.
> 
> I have made a 'small' sample application to demonstrate this, but I
> still use my ODBC wrapper
> classes in that sample application. You may get access to the full
> code. Ask for it!
> 
> The first insert is with valid foreign keys and no column set to NULL.
> This insert works.
> My next insert has set the columns to NULL, but it inserts the values
> of the last insert.

<snip>

> Currently I have made an array of long (cbBufferLength[2]) and set this
> explicitely short before
> the call to SQLSetPos:
> 
> 	if (mode == 1) // 1 means adding
> 		cbBufferLength[1] = SQL_NULL_DATA+SQL_COLUMN_IGNORE;
> 	else
> 		cbBufferLength[0] = SQL_NULL_DATA+SQL_COLUMN_IGNORE;

At first glance, adding SQL_NULL_DATA(=-1) and SQL_COLUMN_IGNORE(=-6)
seems to have no meaning.
If you really want to set to NULL on SQL_ADD, please set SQL_NULL_DATA.
If you want to set DEFAULT on SQL_ADD, please set SQL_COLUMN_IGNORE.

regards,
Hiroshi Inoue

In response to

Responses

pgsql-odbc by date

Next:From: Howard B. GoldenDate: 2006-12-19 00:30:25
Subject: Solution for pgsql odbc driver missing from Windows data sources drivers list
Previous:From: lothar.behrens@lollisoft.deDate: 2006-12-18 22:53:44
Subject: Still SQLSetPos problem even with minimal sample, SQL_NULL_DATA and SQL_COLUMN_IGNORE ?

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