Re: "Official" version - Mailing list pgsql-odbc
From | Scot Loach |
---|---|
Subject | Re: "Official" version |
Date | |
Msg-id | 71837C040963F748B9B94E123A2896785A0FAD@mailserver.sandvine.com Whole thread Raw |
In response to | "Official" version ("Dave Page" <dpage@vale-housing.co.uk>) |
List | pgsql-odbc |
Good point on the declare/fetch usage, obviously this needs to be tried before the driver is considered stable. Same goes for the server-side prepared queries, has anyone tried this feature with the libpq driver? -----Original Message----- From: pgsql-odbc-owner@postgresql.org on behalf of Dave Page Sent: Sat 8/20/2005 4:35 AM To: sfrost@snowman.net; dpage@vale-housing.co.uk Cc: pgsql-odbc@postgresql.org Subject: Re: [ODBC] "Official" version That’s odd - much of my testing has been in Access and i'm unaware of any outstanding issues. Can you provide a minimal pg_dump file containing a table that illustrates the problem please? /D -----Original Message----- From: "Stephen Frost"<sfrost@snowman.net> Sent: 19/08/05 23:11:27 To: "Dave Page"<dpage@vale-housing.co.uk> Cc: "pgsql-odbc@postgresql.org"<pgsql-odbc@postgresql.org> Subject: Re: [ODBC] "Official" version I was playing around with psqlodbclibpq-08_01_0003.zip and seemed to be having problems in Access with it. I'd get errors about a failed command happening inside a transaction and that all commands till the end of the transaction would be ignored. Is there a more recent version of the driver? This is against an 8.0.3 database. Never saw this with the older driver. I got it right off the bat (when getting the table listing in Access to link to) when I had 'declare/fetch' on (which I really need...). When I turned that off I was able to get past the table list and actually link to a table but when I tried to open the table that's what I got. :/ I'd really like to get these issues resolved, of course... Thanks, Stephen -----Unmodified Original Message----- * Dave Page (dpage@vale-housing.co.uk) wrote: > I think it's fairly safe to say that the new libpq version of psqlODBC > is more stable than the previous release versions of the driver, and > also now offers more features such as SSL, Kerberos authentication (has > anyone tried this yet?), pgpass files and so on. > > In light of this, I think the libpq version should now take over as the > official driver, and lose the 'libpq' suffix that was added for testing. > > If anyone has any strong objections, please shriek soon!! I was playing around with psqlodbclibpq-08_01_0003.zip and seemed to be having problems in Access with it. I'd get errors about a failed command happening inside a transaction and that all commands till the end of the transaction would be ignored. Is there a more recent version of the driver? This is against an 8.0.3 database. Never saw this with the older driver. I got it right off the bat (when getting the table listing in Access to link to) when I had 'declare/fetch' on (which I really need...). When I turned that off I was able to get past the table list and actually link to a table but when I tried to open the table that's what I got. :/ I'd really like to get these issues resolved, of course... Thanks, Stephen ---------------------------(end of broadcast)--------------------------- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
pgsql-odbc by date: