From: | Hiroshi Inoue <inoue(at)tpf(dot)co(dot)jp> |
---|---|
To: | the6campbells <the6campbells(at)gmail(dot)com> |
Cc: | pgsql-odbc(at)postgresql(dot)org |
Subject: | Re: bug in sqlDescribeCol for the result set returned by a stored procedure |
Date: | 2009-09-18 15:58:44 |
Message-ID: | 4AB3AE34.2040008@tpf.co.jp |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-odbc |
the6campbells wrote:
> Does not seem to matter if the driver has server side prepare, parse etc
> options enabled.
Unfortunately it seems very difficult to detect that the field
is not null.
regards,
Hiroshi Inoue
> Would someone also confirm if raising bugs via the web page on the
> postgres web site is also for ODBC, JDBC etc issues or not.
>
>
>> Bug reference: 5056
>> Logged by: the6campbells
>> Email address: the6campbells(at)gmail(dot)com
> <mailto:the6campbells(at)gmail(dot)com>
>> PostgreSQL version: 8.4.1
>> Operating system: windows
>> Description: SQLDescribeColW for function returning a result set
>> incorrectly setting sql_nullable
>> Details:
>>
>> create table TSET1 (RNUM integer not null, C1 integer, C2 char(3));
>>
>> create function PRES ( )
>> returns setof TSET1 as
>> '
>> select RNUM, C1, C2 from TSET1;
>> ' LANGUAGE 'sql'
>> ;
>>
>> in ODBC test sqlPrepare { call pres } then describe the columns. first
>> column should be SQL_NO_NULLS not NULLABLE.
>>
>> Describe Column All:
>> icol,
> szColName, *pcbColName, *pfSqlType, *pcbColDef, *pibScale,
>> *pfNullable
>>
> 1, rnum, 4, SQL_INTEGER=4, 10, 0, SQL_NULLABLE=1
>>
> 2, c1, 2, SQL_INTEGER=4, 10, 0, SQL_NULLABLE=1
>>
> 3, c2, 2, SQL_WCHAR=-8, 3, 0, SQL_NULLABLE=1
From | Date | Subject | |
---|---|---|---|
Next Message | Ken Sell | 2009-09-18 16:44:17 | Re: Not able to connect from Informatica |
Previous Message | Hiroshi Inoue | 2009-09-18 15:53:39 | Re: SQLNumResultCol set to 0 for query using common table expression |