Bojan Smojver wrote:
On Thu, 2008-06-12 at 17:54 +0000, [EMAIL PROTECTED] wrote:
+ SQL_C_CHAR, /*SQL_C_TYPE_TIME, /* APR_DBD_TYPE_TIME, \%pDi */
+ SQL_C_CHAR, /*SQL_C_TYPE_DATE, /* APR_DBD_TYPE_DATE, \%pDd */
+ SQL_C_CHAR, /*SQL_C_TYPE_TIMESTAMP, /* APR_DBD_TYPE_DATETIME, \%pDa */
+ SQL_C_CHAR, /*SQL_C_TYPE_TIMESTAMP, /* APR_DBD_TYPE_TIMESTAMP, \%pDs */
+ SQL_C_CHAR, /*SQL_C_TYPE_TIMESTAMP, /* APR_DBD_TYPE_ZTIMESTAMP, \%pDz */
Nested comment?
Actually just supposed to be a reminder that, while ODBC defines bona-fide "C" datatypes for date,
time, & timestamp - DBD currently treats them all as char for now.
I would be happy to take the /*'s out if it's confusing.
Is there a reason not to have /* in a comment? They don't nest in C (but, curiously - they're
suppose to nest in SQL - although few dbs actually do that).
-tom-
