[ psqlodbc-Bugs-1001827 ] Error when updating a TIMESTAMP column with NULL using ADODB

From: <noreply(at)pgfoundry(dot)org>
To: noreply(at)pgfoundry(dot)org
Subject: [ psqlodbc-Bugs-1001827 ] Error when updating a TIMESTAMP column with NULL using ADODB
Date: 2007-03-28 15:55:18
Message-ID: 20070328155518.30A0921752A@pgfoundry.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-odbc

Bugs item #1001827, was opened at 2007-02-05 16:10
You can respond by visiting:
http://pgfoundry.org/tracker/?func=detail&atid=538&aid=1001827&group_id=1000125

Category: None
Group: None
Status: Open
Resolution: None
Priority: 3
Submitted By: Nobody (None)
Assigned to: Nobody (None)
Summary: Error when updating a TIMESTAMP column with NULL using ADODB

Initial Comment:
We are having problems setting TIMESTAMP fields to "Null" using ADODB (from Visual Basic 6)

The attached example doesn't work, it reports an invalid date/time-value.

Setting the field to "null" with an SQL-statement works ("update ..."). It doesn't work with 08_02_0200's Unicode version. The ANSI version works as expected.

The server is running under Linux in version 8.2.0, the clients are running under Windows XP SP2.

----------------------------------------------------------------------

Comment By: Mark Junker (mjcoder)
Date: 2007-03-28 17:55

Message:
I tried psqlODBC from your website which have a date from 2007-03-23 and the problem still exists. I'll attach the logs that were created by the test.

----------------------------------------------------------------------

Comment By: Greg Campbell (grasshopper62)
Date: 2007-03-23 16:50

Message:
Sorry for the confusion,

I suggested trying conn.Execute but I am not the anonymous user who submitted the question. I was just jumped into the thread.

I guess that user who submited teh TestPgOdbc will have to get back to with his MyLog output.

I can say that he was using a connected recordset/cursor technique instead of a disconnected one. Different driver version seem to have trouble with that.

----------------------------------------------------------------------

Comment By: Hiroshi Inoue (hinoue)
Date: 2007-03-23 03:56

Message:
> Instead of recordset.Update, does connection.Execute
work any better?

Maybe but please note your test program TestPgOdbc.exe
works well on my machine. I'd like to know what's happening
on your machine.

regards,
Hiroshi Inoue

----------------------------------------------------------------------

Comment By: Greg Campbell (grasshopper62)
Date: 2007-03-22 17:33

Message:
Instead of recordset.Update, does connection.Execute work any better?

e.g.
conn.Execute "UPDATE SET my_ts_field=NULL"

----------------------------------------------------------------------

Comment By: Hiroshi Inoue (hinoue)
Date: 2007-03-22 01:18

Message:
Hmm it works here.
Could you attach the Mylog output ?

regards,
Hiroshi Inoue

----------------------------------------------------------------------

Comment By: Nobody (None)
Date: 2007-03-21 10:52

Message:
I just downloaded the new drivers (2007-03-21) and repeated the test. Now I get an error "-2147217887". I'll try to translate the error message: "Error in a OLE DB action that consists of multiple steps.". The error occurs when the test application tries to set the field value ("objRs.Fields(txtTableCol.Text) = Null").

----------------------------------------------------------------------

Comment By: Hiroshi Inoue (hinoue)
Date: 2007-02-09 08:44

Message:
PLease try the snapshot dll at
http://www.geocities.jp/inocchichichi/psqlodbc/index.html
.

regards
Hiroshi Inoue

----------------------------------------------------------------------

You can respond by visiting:
http://pgfoundry.org/tracker/?func=detail&atid=538&aid=1001827&group_id=1000125

Browse pgsql-odbc by date

  From Date Subject
Next Message Thomas Günther 2007-03-29 05:59:47 large Objects through ODBC/ADO
Previous Message noreply 2007-03-27 23:28:51 [ psqlodbc-Bugs-1000681 ] Error when using ODBC driver with Microsoft Access