InvalidCastException converting 'CoreLab.Common.DbConnectionClosed' to 'CoreLab.PostgreSql.v'.

Discussion of open issues, suggestions and bugs regarding ADO.NET provider for PostgreSQL
Post Reply
sandeepl
Posts: 4
Joined: Thu 30 Aug 2007 08:18

InvalidCastException converting 'CoreLab.Common.DbConnectionClosed' to 'CoreLab.PostgreSql.v'.

Post by sandeepl » Thu 30 Aug 2007 08:21

Hello,
I get the following exception.
InvalidCastException converting 'CoreLab.Common.DbConnectionClosed' to 'CoreLab.PostgreSql.v'.

I read in one of the earlier posts that this bug has been solved, but I get the same with the latest library that I am using. Pls let me know how to work around this, or if there is another fix for this.

-Sandeep

Alexey
Posts: 2756
Joined: Mon 13 Mar 2006 07:43

Post by Alexey » Thu 30 Aug 2007 09:10

Build with the fix has not been released yet.
Please wait a bit.

sandeepl
Posts: 4
Joined: Thu 30 Aug 2007 08:18

Post by sandeepl » Thu 30 Aug 2007 09:12

Hello Alexey,
Is there a work around for this since we are considering buying site license for your drivers and we are in the middle of migrating our DB from sql server to postgres.

-Sandeep

Alexey
Posts: 2756
Joined: Mon 13 Mar 2006 07:43

Post by Alexey » Thu 30 Aug 2007 09:22

We are going to release PostgreSQLDirect .NET 3.20 tonight.

P.S. I can't guarantee that our fix definitely resolves the problem you encountered. Are you sure it occurs under the same circumstances as described in that post? Could you send me a test project to reproduce the problem?
Use email address provided in the Readme.txt file.
Last edited by Alexey on Fri 31 Aug 2007 08:55, edited 1 time in total.

sandeepl
Posts: 4
Joined: Thu 30 Aug 2007 08:18

Post by sandeepl » Fri 31 Aug 2007 06:07

Hello Alexey,
I tried to build a simple project that can consistently reproduce the issue, but I cannot reproduce the same always. Also to note is that I am trying to keep the code provider independent and so use only the DbConnect, DbTable etc classes. Also of interest is that only one table out of about 100 gives the trouble. The structure of that table is below. A "select * from ipList" query to create a DbTable and doing a DbDataAdapter.Fill() results in the exception mentioned.

CREATE TABLE iplist
(
ipaddress character varying(50) NOT NULL,
macaddress character varying(50),
loadtime timestamp without time zone,
CONSTRAINT iplist_pkey PRIMARY KEY (ipaddress)
)
WITH (OIDS=FALSE);
ALTER TABLE iplist OWNER TO postgres;

Alexey
Posts: 2756
Joined: Mon 13 Mar 2006 07:43

Post by Alexey » Fri 31 Aug 2007 08:49

Does the problem persist with 3.20 version?

Post Reply