Re: Problems about ODBC3 datetime - Mailing list pgsql-odbc

From Hiroshi Inoue
Subject Re: Problems about ODBC3 datetime
Date
Msg-id EKEJJICOHDIEMGPNIFIJAEMPJMAA.Inoue@tpf.co.jp
Whole thread Raw
In response to Problems about ODBC3 datetime  ("Han" <zhouhanok@vip.sina.com>)
List pgsql-odbc
> -----Original Message-----
> From: Han
>
> Hi,
>     Firstly, I encountered a problem when using SQL_DATE: when
> I use SQLGetTypeInfo(...,SQL_DATE);
> the API returns no record. I debuged the psqlodbc driver and
> found that the value of the parameter DataType was 91. So I think
> that the value was changed by the odbc30 Driver Manager. But why
> don't the psqlodbc add the SQL_TYPE_DATE and other ODBC30 data
> types support in the array sqlTypes[](in pgtypes.c)?

Hmm you seem to be right. I would add SQL_TYPE_DATE, SQL_TYPE_TIME
and SQL_TYPE_TIMESTAMP to sqlTypes[].

>     Secondly, I wander why returning SQL_DATETIME in function
> pgtype_to_sqldesctype for the three types--SQL_TYPE_DATE,
> SQL_TYPE_TIME, SQL_TYPE_TIMESTAMP?

There are SQL_DESC_TYPE and SQL_DESC_CONCISE_TYPE in ODBC3
and
  If SQL_DESC_CONCISE_TYPE is set to a concise data type other than an
  interval or datetime data type, the SQL_DESC_TYPE field is set to the same
  value and the SQL_DESC_DATETIME_INTERVAL_CODE field is set to 0.

  If SQL_DESC_CONCISE_TYPE is set to the concise datetime or interval data
  type, the SQL_DESC_TYPE field is set to the corresponding verbose type
  (SQL_DATETIME or SQL_INTERVAL) and the SQL_DESC_DATETIME_INTER
  VAL_CODE field is set to the appropriate subcode.

regards,
Hiroshi Inoue


pgsql-odbc by date:

Previous
From: "Alan R. Johns"
Date:
Subject: Re: empty text on XP in MS Access
Next
From: "Hiroshi Inoue"
Date:
Subject: Re: empty text on XP in MS Access