Apologies for re-posting... I fat-fingered the odbc list address :-/

Hi all. I having an issue with the 8.01.01.02 ODBC driver that is
installed via the 8.1.x Windows installer.

Whenever there is an error on the connection (eg: trying to execute a
sql statement that has a syntax error as an example) the
System.Data.OdbcConnection object throws an exception - which is
entirely expected. However, the error message returned is "The
connection is dead". I have to go into the postgresql log files to try
and locate the actual error.

The same code used to work (meaning it returned the text of the
postgresql error message in the exception) for me with 8.0.x so I'm
kind of at a loss as to what has changed that would cause this
behavior.

Anyone have any ideas whats going on or how I can get back to the 8.0.x

behavior?

__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com

---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?

http://www.postgresql.org/docs/faq

> Hi all. I having an issue with the 8.01.01.02 ODBC driver that is
> installed via the 8.1.x Windows installer.

....

> Anyone have any ideas whats going on or how I can get back to the 8.0.x
> behavior?

There is newer 08.01 psqlODBC version. Please try the 08.01.0200 version.
We provide a lot of changes (including error reporting).

Feel free to re-post the message if 08.01.0200 is still boken. I'll
appreciate if you include mylog output (from 08.01.0200 driver).

Regards,

Luf

---------------------------(end of broadcast)---------------------------
TIP 2: Don't 'kill -9' the postmaster

--- Ludek Finstrle <luf@pzkagis.cz> wrote:

> > Hi all. I having an issue with the 8.01.01.02 ODBC driver that is
> > installed via the 8.1.x Windows installer.
>
> ...
>
> > Anyone have any ideas whats going on or how I can get back to the
> 8.0.x
> > behavior?
>
> There is newer 08.01 psqlODBC version. Please try the 08.01.0200
> version.
> We provide a lot of changes (including error reporting).
>
> Feel free to re-post the message if 08.01.0200 is still boken. I'll
> appreciate if you include mylog output (from 08.01.0200 driver).
>
> Regards,
>
> Luf
>

Thanks. I'll try the new version out and let you know.

__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com

---------------------------(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

> > Feel free to re-post the message if 08.01.0200 is still boken. I'll
> > appreciate if you include mylog output (from 08.01.0200 driver).
>
> Using 08.01.0200, I'm still receiving the same error. However, I've
> managed to narrow the case when it happens down a bit. I only receive
> the "The connection is dead" error when an error occurs after I've
> explicitly defined a transaction via ADO.Net's
> OdbcConnection.BeginTransaction() function.

Interesting. I see no such call in ODBC.

> I'd be happy to send you a small C# test case in if you wish.

It would be the shortest way for me.

Thanks,

Luf

---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?

http://www.postgresql.org/docs/faq

--- Ludek Finstrle <luf@pzkagis.cz> wrote:

> > I'd be happy to send you a small C# test case in if you wish.
>
> It would be the shortest way for me.
>

Sent offlist.

__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com

---------------------------(end of broadcast)---------------------------
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo@postgresql.org so that your
message can get through to the mailing list cleanly