Bug #725: ODBC driver problem with internal type PG_TYPE_TIMESTAMP_NO_TMZONE

This has been corrected in the current sources at odbc.postgresql.org.

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

pgsql-bugs@postgresql.org wrote:

Martin Schenk (martin@schenk.com) reports a bug with a severity of 2
The lower the number the more severe it is.

Short Description
ODBC driver problem with internal type PG_TYPE_TIMESTAMP_NO_TMZONE

Long Description
When binding a column with the internal type PG_TYPE_TIMESTAMP_NO_TMZONE to a SQL_C_TIMESTAMP variable, you always get the current date/time as result.

Adding a line to recognize this format to the function "copy_and_convert_field" in odbc/convert.c solves this problem.

Sample Code
the problem is solved by adding the following:

case PG_TYPE_ABSTIME:
case PG_TYPE_DATETIME:
case PG_TYPE_TIMESTAMP:
+ case PG_TYPE_TIMESTAMP_NO_TMZONE

in file convert.c (line 428), function "copy_and_convert_field"
(odbc driver shipped with postgres-7.2.1)

No file was uploaded with this report

---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo@postgresql.org so that your
message can get through to the mailing list cleanly

-- 
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 359-1001
  +  If your life is a hard drive,     |  13 Roberts Road
  +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073