Discussion of open issues, suggestions and bugs regarding ADO.NET provider for PostgreSQL
-
AndreyR
- Devart Team
- Posts: 2919
- Joined: Mon 07 Jul 2008 13:16
Post
by AndreyR » Wed 29 Jun 2011 15:51
The issue is associated with the fact that Code First uses a different approach to create a command, and our functionality did not cover this use case.
The workaround I have already suggested allows for these peculiarities.
-
cjbiggs
- Posts: 105
- Joined: Fri 15 Jan 2010 19:56
Post
by cjbiggs » Wed 29 Jun 2011 16:34
But my use case have worked before and I have verified that it worked when you said that it was fixed and sent me a test application that I verified that worked. Did it ever work or
Thanks,
Charlie J.
-
AndreyR
- Devart Team
- Posts: 2919
- Joined: Mon 07 Jul 2008 13:16
Post
by AndreyR » Fri 01 Jul 2011 15:06
Is the problem resolved with using PgSqlEntityProviderServices?
We are working on the improvement of the UnpreparedExecute connection string parameter.
-
cjbiggs
- Posts: 105
- Joined: Fri 15 Jan 2010 19:56
Post
by cjbiggs » Fri 08 Jul 2011 13:34
Yes. The problem is resolved by using the PgSQLEntityProviderServices in the constructor of the EF Context.
When will the UnpreparedExecute connection string parameter function the same way without put this workaround in the constructor of the EF Context?
Thanks,
Charlie J.
-
AndreyR
- Devart Team
- Posts: 2919
- Joined: Mon 07 Jul 2008 13:16
Post
by AndreyR » Mon 11 Jul 2011 10:03
We will post here when this functionality is implemented.
The investigation is in progress.
-
cjbiggs
- Posts: 105
- Joined: Fri 15 Jan 2010 19:56
Post
by cjbiggs » Thu 15 Sep 2011 14:32
Any updates on When will the UnpreparedExecute connection string parameter function the same way without put this workaround in the constructor of the EF Context?
Thanks,
Charlie J.
-
Shalex
- Site Admin
- Posts: 9543
- Joined: Thu 14 Aug 2008 12:44
Post
by Shalex » Mon 19 Sep 2011 14:10
We are working on this issue. We will notify you about the results as soon as possible.
-
Shalex
- Site Admin
- Posts: 9543
- Joined: Thu 14 Aug 2008 12:44
Post
by Shalex » Thu 22 Sep 2011 15:58
The bug with assigning the UnpreparedExecute option from connection string to the command is fixed. We will post here when the corresponding build of dotConnect for PostgreSQL is available for download.