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: Some changes |
Date: | 2005-12-02 14:57:18 |
Message-ID: | E7F85A1B5FF8D44C8A1AF6885BC9A0E4E7E5F4@ratbert.vale-housing.co.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-odbc |
> -----Original Message-----
> From: Ludek Finstrle [mailto:luf(at)pzkagis(dot)cz]
> Sent: 02 December 2005 14:38
> To: Dave Page
> Cc: pgsql-odbc(at)postgresql(dot)org
> Subject: Re: [ODBC] Some changes
>
> > The attached patch clears out any parameters during SQLCancel. This
> > works for the test case, and seems to not hurt any of my
> apps that I've
> > quickly tested. I definitely want some feedback before I apply this
> > though please :-)
>
> I see (endly) ODBC specification and it's ok to free all parameters
> when SQLCancel is called during awaiting data (SQL_NEED_DATA).
> Only comment in patch is little bit strenge.
>
> I have to more study ODBC specification. It's mine bottleneck.
And mine :-(. I'm pretty sure the patch is within the spec though (and
frankly, I'm more concerned that the driver works as most popular
applications expect than 100% to the spec which is pretty much the line
taken by previous maintainers).
Anyhoo, please let me know if you think it's good to apply when you've
taken a look at it - I'd appreciate the feedback on this one!
Regards, Dave
From | Date | Subject | |
---|---|---|---|
Next Message | Andrus | 2005-12-02 16:51:26 | Re: Application crash after error - please help |
Previous Message | Ludek Finstrle | 2005-12-02 14:37:59 | Re: Some changes |