Postby witte » Tue 04 Aug 2009 12:34

I've downloaded the demo driver for testing its usability in production environments. During checking I've found that the also appear in this postgresql-release:
At the end of this blog entry one could read that the fix will or may be implemented in the next release for mysql. Now the next release for postgresql is published and the bug still occurs. Can that be fixed for postgrsql too in the next version?
Posts: 1
Joined: Tue 04 Aug 2009 11:50

Postby AndreyR » Thu 06 Aug 2009 12:41

This problem will be fixed in the next build of dotConnect for PostgreSQL (not the current 4.55.39 one).
Devart Team
Posts: 2919
Joined: Mon 07 Jul 2008 13:16

Return to dotConnect for PostgreSQL