From: | Dave Page <dpage(at)vale-housing(dot)co(dot)uk> |
---|---|
To: | Ludek Finstrle <luf(at)pzkagis(dot)cz> |
Cc: | <pgsql-odbc(at)postgresql(dot)org> |
Subject: | Re: Disallow premature is broken |
Date: | 2006-01-28 21:25:58 |
Message-ID: | C00191E6.49FC%dpage@vale-housing.co.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-odbc |
On 27/1/06 22:38, "Ludek Finstrle" <luf(at)pzkagis(dot)cz> wrote:
> Fri, Jan 27, 2006 at 09:39:05AM -0000, Dave Page wrote:
>>> What do you think? How do we want change the behaviout before
>>> releasing new stable release? I'm not sure. There is no much time
>>> for testing new behaviour. The multistatements hasn't been reported
>>> yet by users. It seems this feature isn't widely used.
>>
>> In the short term though, I say just stop it crashing and let's get a
>> release out seeing as Tom is getting antsy about FC5 :-)
>
> Here is the patch. I'll include it into 08.01.0108 dev snapshot.
> psqlodbc doesn't fall down on exception when "Disallow premature"
> is checked and: SQLPrepare, SQLNumResultCols is called.
> The SQLNumResultCols returns SQLSTATE HY0000 with message like
> No result was returned by the query.
>
> Please review and comment
Looks like a perfectly fine temporary fix.
Regards, Dave.
From | Date | Subject | |
---|---|---|---|
Next Message | noreply | 2006-01-30 07:35:33 | [ psqlodbc-Bugs-1000528 ] Link with Microsoft Access always broke |
Previous Message | Tom Lane | 2006-01-28 17:25:08 | Re: SQLGetInfo buffer overflow? |