From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | the6campbells <the6campbells(at)gmail(dot)com> |
Cc: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: BUG #5056: SQLDescribeColW for function returning a result set incorrectly setting sql_nullable |
Date: | 2009-09-15 02:51:28 |
Message-ID: | 603c8f070909141951j17f163aboc3315f70bf908c67@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Mon, Sep 14, 2009 at 10:40 PM, the6campbells <the6campbells(at)gmail(dot)com> wrote:
>
> The following bug has been logged online:
>
> Bug reference: 5056
> Logged by: the6campbells
> Email address: 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
I think you may want to try here, for both this and your previous bug report.
pgsql-odbc(at)postgresql(dot)org
http://archives.postgresql.org/pgsql-odbc/
...Robert
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2009-09-15 03:20:59 | Re: [BUGS] BUG #5053: domain constraints still leak |
Previous Message | the6campbells | 2009-09-15 02:40:21 | BUG #5056: SQLDescribeColW for function returning a result set incorrectly setting sql_nullable |