|
Home > Archive > PostgeSQL ODBC > November 2005 > Problems with MDAC and lo
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Problems with MDAC and lo
|
|
| Alessandro Pedroso 2005-11-04, 3:23 am |
| Hi
Sorry for my poor english
I' ve tried to work with 8.1.0006 version and 0005 too, but , when i
tried to use ClientCursor on ADO connection this not work properly. If i
turn off Disallow Premature option on ODBC, works fine, but very slow.
Another versions before 8.1xxx works fine too.
What's happen?
Thanks
--
This e-mail was scanned with a private,
non-commercial version of AntiVir MailGate.
See http://www.antivir.de for details.
---------------------------(end of broadcast)---------------------------
TIP 2: Don't 'kill -9' the postmaster
| |
| Dave Page 2005-11-04, 3:23 am |
|
> -----Original Message-----
> From: pgsql-odbc-owner@postgresql.org
> [mailto:pgsql-odbc-owner@postgresql.org] On Behalf Of
> Alessandro Pedroso
> Sent: 04 November 2005 01:20
> To: pgsql-odbc@postgresql.org
> Subject: [ODBC] Problems with MDAC and lo
>
> Hi
>
> Sorry for my poor english
>
> I' ve tried to work with 8.1.0006 version and 0005 too,
> but , when i
> tried to use ClientCursor on ADO connection this not work
> properly. If i
> turn off Disallow Premature option on ODBC, works fine, but very slow.
> Another versions before 8.1xxx works fine too.
>
> What's happen?
ClientCursor work fine here with or without Disallow Premature. Can you
provide any sample code/schema?
Regards, Dave.
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
|
|
|
|
|