Npgsql 2.2.2 has just been released and is available via nuget.

This is a bugfix-only release which corrects some issues found since 2.2.1.

Npgsql 2.2.1 has just been released and is available via nuget.

This is a bugfix-only release which corrects some issues found since 2.2.0.

This is Npgsql 2.2.0 Final Release

UPDATE (2014-09-06): Kenji Uno made an installer available which helps users to setup Npgsql to work with VS.Net Database Designer as well as EntityFramework. You can find more information about this installer here. You can find the installer in the downloads section.

This release contains 249 commits since the last stable release. Includes bug fixes, improvements and new features.

Update notice: If you have been using Npgsql 2.2.0-rc2, you don't need to update to this version. They are the same except for the Assembly version information.

Major highlights

Visual Studio DDEX support

Kenji Uno added support for DDEX. Now you can use Npgsql with Visual Studio data designer. This is a missing feature a lot of our users requested in the past. Kenji added a tutorial about how to use Npgsql with DDEX. You can find it here: https://github.com/npgsql/Npgsql/wiki/Visual-Studio-Design-Time-Support---DDEX-Provider#install-npgsqlddexprovidervsix

Entity Framework

David Karlaš added support for EFMigration and Database creation in EF6+.
Now it is possible to start Code First projects without needing to create a database upfront. EntityFramework and Npgsql will take care of it.
Emil Lenngren added support for a lot of missing features of EntityFramework.

A list containing fixes from David and Emil as well as others for EntityFramework can be seen here: https://github.com/npgsql/Npgsql/issues?direction=desc&labels=entity+framework&milestone=2&page=1&sort=created&state=closed

SSLStream support

In this release, SSLStream is on by default.
If you want to use Mono.Security, you will need to use the following line in your code:

NpgsqlConnection.UseSslStream = false;

Note that in future releases, this option may not be available anymore as we are removing the dependency on Mono.Security assembly. Let us know in the forums if you have any problem with ssl when using SSLStream. This will help us check if we will be able to remove Mono.Security assembly.

Added support for JSON, JSONB and HSTORE datatypes

Shay added support for those datatypes.

Added GSSAPI support on Windows

Brian Crowell added support for GSSAPI on windows. Now it is easier to use Active Directory when authenticating users.

Removed support for protocol v2

Postgresql versions which use only protocol 2 are very old and don't receive support from postgresql group anymore. By removing support for protocol version 2, we removed a lot of code and can focus on functionalities provided by protocol 3.

Removed support for Postgresql 8.4 and below

In this thread, we talked about making Npgsql support the officially supported postgresql versions. we talked about making Npgsql support the officially supported postgresql versions. Postgresql has a table of officially supported versions and we decided to follow this table to guide us which postgresql version we will have support to.

This doesn't necessarily mean that Npgsql won't work on unsupported versions. It may work if we don't add any SQL or unsupported feature. For example, today Npgsql 2.2 works only on Postgresql 8.2 and above because we added server side support for command timeout handling and some other queries which aren't supported on earlier versions.

If you are using earlier postgresql versions, please, use an older version of Npgsql. We are creating a compatibility table to show which Postgresql version Npgsql works with.

Fixed bugs:

[#91] Support for EFMigration and Database creation
[#152] NpgsqlInterval different constructors different ToString
[#158] NpgsqlCommand.Dispose() should execute "DEALLOCATE " for a prepared command
[#177] XML data type doesn't seem to be quoting parameters properly on insert
[#179] NpgsqlCommandBuilder automatic sql commands configuration
[#188] Buffer too small problem in NpgsqlCopySerializer
[#201] Dynamic type parameters: Cannot cast System.Int32 into any valid DbType after upgrading from 2.0.14.3 to 2.1.2.0
[#208] ObjectDisposeException
[#217] Impossible to insert a Double.NaN value
[#219] [#1011005] using 2 NpgsqlCopyIn at the same time
[#223] HasRows property's bug
[#231] NpgsqlParameterCollection.Clear() doesn't reset NpgsqlParameter.Collection
[#225] Handle IEnumerable parameter
[#233] Cannot insert to tables which have only one column
[#246] Take followed by Skip is generated incorrectly in Entity Framework
[#262] FirstOrDefault() on navigation property subquery throws “Not Implemented” Exception
[#264] Mono.Security is outdated
[#269] Fix 's' value mapped to the 'a' byte
[#280] Bad SQL produced when selecting a field that was also used in the orderBy of a let subquery
[#287] Fix operator handling and date functions for EF
[#296] parameter parsing fails (regression) and duplicate [#240] NpgSqlCommand does not substitute parameters when there is a string with escaped apostrophe
[#315] Fix query parameter processing to more correctly match PostgreSQL's lexer

A list of the issues and pull requests merged for this release can be found at github here: https://github.com/npgsql/Npgsql/issues?direction=desc&milestone=2&page=1&sort=created&state=closed

Known Issues

There are some issues we are working for the next maintenance release 2.2.1. You can check which issues we are working on here: https://github.com/npgsql/Npgsql/issues?q=milestone%3A2.2.1

Thanks

I'd like to give a special thanks to Kenji Uno for his excellent work with Npgsql DDEX support. DDEX support was one of the biggest missing features of Npgsql.

I'd like to thank Emil Lenngren for all his work with Entity Framework improvements and insightful comments, David Karlaš for his help with Entity Framework support. Shay Rojansky, Glen Parker and Josh Cooley for all contributions and comments, and a big thanks to all the other contributors who helped us to make this release.

List of contributors for this release

Kenji Uno
Shay Rojansky
Glen Parker
Emil Lenngren
David Karlaš
Brian Crowell
danzel
Tuan Nguyen
windcloud
asgeirh
Frans Bouma
Jaspalsinh Chauhan
Josh Cooley
Martin Willey
Francisco Figueiredo Jr.
shankbond
Javier Torres
Kevin Pullin
Michael de Lang
Oskar Gewalli
Sunny Ahuwanya
Thomas Radioyes
javitonino
mw
samy

This is the second release candidate (RC) of Npgsql 2.2

This release contains 9 commits since the last release. Includes the following bug fixes:

[#233] Cannot insert to tables which have only one column
[#315] Fix query parameter processing to more correctly match PostgreSQL's lexer

This is the first release candidate (RC) of Npgsql 2.2

This release contains 22 commits since the last release. Includes the following bug fixes:

[#217] Impossible to insert a Double.NaN value
[#179] NpgsqlCommandBuilder automatic sql commands configuration
[#158] NpgsqlCommand.Dispose() should execute "DEALLOCATE " for a prepared command
[#264] Mono.Security is outdated
[#296] parameter parsing fails (regression) and duplicate [#240] NpgSqlCommand does not substitute parameters when there is a string with escaped apostrophe

A complete list of commits for this release can be found here: https://github.com/npgsql/Npgsql/compare/v2.2.0-beta1...release-2.2.0

This is the first beta of Npgsql 2.2

This release contains 182 commits since the last release. Includes bug fixes, improvements and new features.

Major highlights

Visual Studio DDEX support

Kenji Uno added support for DDEX. Now you can use Npgsql with Visual Studio data designer. This is a missing feature a lot of our users requested in the past. Kenji added a tutorial about how to use Npgsql with DDEX. You can find it here: https://github.com/npgsql/Npgsql/wiki/Visual-Studio-Design-Time-Support---DDEX-Provider#install-npgsqlddexprovidervsix

Entity Framework

David Karlaš added support for EFMigration and Database creation in EF6+

Now it is possible to start Code First projects without needing to create a database upfront. EntityFramework and Npgsql will take care of it.
Emil Lenngren added support for a lot of missing features of EntityFramework.

A list containing fixes from David and Emil as well as others for EntityFramework can be seen here: https://github.com/npgsql/Npgsql/issues?direction=desc&labels=entity+framework&milestone=2&page=1&sort=created&state=closed

SSLStream support

In this release, SSLStream is on by default.
If you want to use Mono.Security, you will need to use the following line in your code:

NpgsqlConnection.UseSslStream = false;

Note that in future releases, this option may not be available anymore as we are removing the dependency on Mono.Security assembly. Let us know in the forums if you have any problem with ssl when using SSLStream. This will help us check if we will be able to remove Mono.Security assembly.

Added support for JSON, JSONB and HSTORE datatypes

Shay added support for those datatypes.

Added GSSAPI support on Windows

Brian Crowell added support for GSSAPI on windows. Now it is easier to use Active Directory when authenticating users.

Removed support for protocol v2

Postgresql versions which use only protocol 2 are very old and don't receive support from postgresql group anymore. By removing support for protocol version 2, we removed a lot of code and can focus on functionalities provided by protocol 3.

Removed support for Postgresql 8.3 and below

In this thread, we talked about making Npgsql support the officially supported postgresql versions. we talked about making Npgsql support the officially supported postgresql versions. Postgresql has a table of officially supported versions and we decided to follow this table to guide us which postgresql version we will have support to.

This doesn't necessarily mean that Npgsql won't work on unsupported versions. It may work if we don't add any SQL or unsupported feature. For example, today Npgsql 2.2 works only on Postgresql 8.2 and above because we added server side support for command timeout handling and some other queries which aren't supported on earlier versions.

If you are using earlier postgresql versions, please, use an older version of Npgsql. We are creating a compatibility table to show which Postgresql version Npgsql works with.

Fixed bugs:

[#91] Support for EFMigration and Database creation
[#152] NpgsqlInterval different constructors different ToString
[#177] XML data type doesn't seem to be quoting parameters properly on insert
[#188] Buffer too small problem in NpgsqlCopySerializer
[#201] Dynamic type parameters: Cannot cast System.Int32 into any valid DbType after upgrading from 2.0.14.3 to 2.1.2.0
[#208] ObjectDisposeException
[#219] [#1011005] using 2 NpgsqlCopyIn at the same time
[#223] HasRows property's bug
[#231] NpgsqlParameterCollection.Clear() doesn't reset NpgsqlParameter.Collection
[#225] Handle IEnumerable parameter
[#246] Take followed by Skip is generated incorrectly in Entity Framework
[#262] FirstOrDefault() on navigation property subquery throws “Not Implemented” Exception
[#269] Fix 's' value mapped to the 'a' byte
[#280] Bad SQL produced when selecting a field that was also used in the orderBy of a let subquery
[#287] Fix operator handling and date functions for EF

A list of the issues and pull requests merged for this release can be found at github here: https://github.com/npgsql/Npgsql/issues?direction=desc&milestone=2&page=1&sort=created&state=closed

Known Issues

There are still some issues we need to check before the final release. You can check which issues we are still working on here: https://github.com/npgsql/Npgsql/issues?direction=desc&milestone=2&page=1&sort=created&state=open

Thanks

I'd like to give a special thanks to Kenji Uno for his excellent work with Npgsql DDEX support. DDEX support was one of the biggest missing features of Npgsql.

I'd like to thank Emil Lenngren for all his work with Entity Framework improvements and insightful comments, David Karlaš for his help with Entity Framework support. Shay Rojansky, Glen Parker and Josh Cooley for all contributions and comments, and a big thanks to all the other contributors who helped us to make this release.

List of contributors for this release

Kenji Uno
Shay Rojansky
Glen Parker
Emil Lenngren
David Karlaš
Brian Crowell
danzel
Tuan Nguyen
windcloud
asgeirh
Frans Bouma
Jaspalsinh Chauhan
Josh Cooley
Martin Willey
Francisco Figueiredo Jr.
shankbond
Javier Torres
Kevin Pullin
Michael de Lang
Oskar Gewalli
Sunny Ahuwanya
Thomas Radioyes
javitonino
mw
samy

This version restores support for @@ operator (#135) which was removed in the previous version.

This version contains fixes for #165 (KeyNotFoundException when setting ApplicationName on NpgsqlConnectionStringBuilder) and a regression when using NHibernate with queries containing '<' operator. #193 (Less Than' prepare failing).

Note that version breaks support to @@ operator added by #135 . Glen Parker is working in a full solution which adds #135 support back. If you need #135 support, please, use the 2.1.1 version. Sorry for this problem.

This release contains a single last minute patch to fix HasRows property: Return true from NpgsqlDataReader.HasRows even after all rows have been read https://github.com/npgsql/Npgsql/pull/181

If you aren't affected by this bug, you don't need to download this version again.

Summary:

This is a the final release of Npgsql 2.1.0

Thanks

Before talking about the changes in this release, I'd like to thank some people who did an incredible job and that without them this release wouldn't be possible!

Glen Parker has been working in the optimizations tasks since his first git commit. From the changelog you can see his tireless work regarding each part of Npgsql which could be optimized. Thank you very much for your contributions, Glen!

Shay Rojansky has been helping as the mastermind of the project restructuring support. He contributed a lot of changes which made our lives working with Npgsql much better. Thanks to him we can compile Npgsql for different .net platform versions easily. He also got TeamCity build server working as well as github integration. He helped us to get EntityFramework pre-6 and pos-6 verions easily integrated.
Thank you, Shay!

And Dave Page who helped us with the server where the TeamCity is installed. Without his help, I'm sure our TeamCity installation would be much more difficult. Thank you, Dave!

Major highlights

Version numbers

Starting with this release, we are going to number our versions based on the semver schema. (http://semver.org). We may not follow strictly everything though. This is a work in progress.

This version was supposed to be a continuation of the 2.0.13 series as we already have a 2.0.13 beta1 released. But we made so many changes since the 2.0.13 that we decided to jump the version number to 2.1.

Entity Framework

We added initial support for Entity Framework 6.0. We isolated the entity framework code in two other assemblies: Npgsql.LegacyEntityFramework.dll and Npgsql.EntityFramework.dll. The first one is for entity framework pre-6 version and the other one is for entity framework 6.0 and above. This was needed in order to facilitate the deployment and the code organization as the apis and namespaces change a lot depending on the entity framework version.

Support for 6.0 isn't yet complete and is to be considered optional at the moment. We will add better support in upcoming versions. We already have Support for EFMigration and Database creation (https://github.com/npgsql/Npgsql/pull/91) and identity insert support (https://github.com/npgsql/Npgsql/pull/160) which will be made available in future releases of Npgsql

Entity Framework configuration

App.config and Web.config configuration has been changed. It depends on the EF version you are using. More info about that can be found at:
http://fxjr.blogspot.com.br/2014/02/using-entity-framework-6-with-npgsql-210.html

SSLStream support

In this release, we added support to use SSLStream. But it isn't used by default. To keep backward compatibility, we still use by default Mono.Security for SSL connections. But this may change in the future. We ask that you test your application with SSLStream and check if you get any problems.
in order to use SSLStream, you have to ask Npgsql to use it by using the following line:

NpgsqlConnection.UseSslStream = true

This will make Npgsql use SSLStream for new ssl connections.
Please, give it a try and let us know if it works ok for you.

Project restructuring

Npgsql had its project layout restructured to easy management of different platforms Npgsql targets: .net 2.0, 3.5, 4.0, 4.5, entity framework prior 6.0, entity framework after 6.0. Huge structure changes to our testsuite. Before, our tests depended on an external script to setup database tables, now everything is done inside the tests setup. Thanks Shay Rojansky.

Fixed bugs:

[#176] 2.1 RC SSL and EF6 no work.
[#174] GetResultSchema When current description is null
[#164] Connection state throws error incorrectly
[#181] Return true from NpgsqlDataReader.HasRows even after all rows have been read

[#28] [#1011338] Error in insert statement with new E6 version. Thanks cody82.
[#27] Fixed connecting to Postgresql using client certificates. Check http://fxjr.blogspot.com.br/2013/07/sslstream-support-added-to-npgsql.html for more information. Thanks dreamlax
Added VS2012 project file. Thanks Glen Parker
[#35] Fixed array handling with prepared statements. Thanks Chen Huajun.
[#33] [#1011346] BUGFIX: Thread synchronization inside GetPooledConnector
[#57] Bytea handling optimizations. Thanks Rungee
[#59] Bytea decoder optimizations. Thanks Glen Parker
[#1000515] Prepare() makes command very slow. Thanks Glen Parker for optimizations.
[#61] Async notification optimizations and fixes. Glen Parker
[#63] [#1011334] NpgsqlConnection.GetSchema doesn't dispose connections
[#69] Fix extra-float-digits setup for postgresql below 9.0
[#92] Added InvariantCulture to NpgsqlCopySerializer. Thanks djsubzero
[#86] Rewrite query parameter substitution. Thanks Glen Parker
[#118] Detection of Parameter Direction in DeriveParameters method. Thanks Noé Garcia and Shay Rojansky
[#1011271] NpgsqlSchema: Use InvariantCulture on all return DataTables with schema data. Thanks Oskar Berggren for patch.
[#1011305] Scope without prepared transactions. Thanks Shay Rojansky for the patch.
[#1011310] Command timeouts after the first are not handled. Thanks Evan Martin for the patch.
[#1011316] ConnectionTimeout fix, bypass the 2147 seconds limit of Socket.Poll method. Thanks Tasos Mamaloukos for patch.
[#1011325] Escaped strings don't work with EF. Thanks Andrey Polyakov for patch and tests.
Implements DateTime canonical functions for EntityFramework. Thanks Andrey Polyakov for patch.
[#1011325] Escaped strings don't work with EF. Thanks Andrey Polyakov for patch and tests.
[#1011321] Wrong BitString value. Thanks Jon Hanna for patch and support.
[#1011326] Connection pooling timer (thus thread) is active even if connection pooling is disabled. Thanks Shay Rojansky for the patch.
[#1011001] Bug in NpgsqlConnectionStringBuilder affects on cache and connection pool. Thanks Shay Rojansky for the patch.
[#1011267] Monetary localization bug
[#1011085] Money format is not set in accordance with the system locale format

New features:

Add support for new error fields added in PostgreSQL 9.3. See here for more information about those fields: http://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=991f3e5ab3f8196d18d5b313c81a5f744f3baaea Thanks David Rowley for patch.

Initial support for Entity Framework 6. See http://fxjr.blogspot.com/2013/06/initial-ef-6-support-added-to-npgsql.html for more information about it.

[#30] Improved connection timeout handling. Thanks Glen Parker.

[#41], [#52], [#77], [#72], [#80] Huge internal query handling which added a big performance boost for prepared statements and unprepared statements as well. Binary parameter codec infrastructure has been added, and several data types (currently bytea, text, boolean, integers, and gloats) can now use PG's binary coded support, including arrays of those types, which offers a dramatic performance boost for parameter and result values in prepared statements. Previously we didn't recommend using prepared statements with Npgsql, only for bytea data types. Thanks to Glen Parker, this is now a thing of the past.

[#74] Use new "Discard all" syntax when releasing connection from pool. Thanks Chen Huajun.

New connection string parameter "AlwaysPrepare" to indicate to Npgsql to always prepare statements before executing.

[#110] Added support for Entity Framework before version 6.0 and after 6.0. They are totally different things regarding APIs and namespaces. Thanks Shay Rojansky and Kenji Uno.

Added nuget EFProvider installation. Thanks Shay Rojansky.

Added EF6 ConnectionFactory class. Thanks Shay Rojansky.

[#135] Fix for operators @@, @> and <@. Thanks Glen Parker and jjchiw.

[#117] Command timeout improvements. Thanks Glen Parker.

Summary:

This is a bug fix release for 2.1.0-beta1, and the first 2.1 Release Candidate.

Fixed bugs:

#141 AlwaysPrepare does not works in some cases. Thanks @avb1987.
#153 Fixed wrong comma putting in AddFunctionColumnListSupport(). Thanks @tyler-nguyen.

Npgsql 2.1.0 (beta1)

Major highlights

Version numbers

Starting with this release, we are going to number our versions based on the semver schema. (http://semver.org). We may not follow strictly everything though. This is a work in progress.

This version was supposed to be a continuation of the 2.0.13 series as we already have a 2.0.13 beta1 released. But we made so many changes since the 2.0.13 that we decided to jump the version number to 2.1.

Entity Framework

We added initial support for Entity Framework 6.0. We isolated the entity framework code in two other assemblies: Npgsql.LegacyEntityFramework.dll and Npgsql.EntityFramework.dll. The first one is for entity framework pre-6 version and the other one is for entity framework 6.0 and above. This was needed in order to facilitate the deployment and the code organization as the apis and namespaces change a lot depending on the entity framework version.

Support for 6.0 isn't yet complete and is to be considered optional at the moment. We will add better support in upcoming versions.

Fixed bugs:

[#28] [#1011338] Error in insert statement with new E6 version. Thanks cody82.
[#27] Fixed connecting to Postgresql using client certificates. Check http://fxjr.blogspot.com.br/2013/07/sslstream-support-added-to-npgsql.html for more information. Thanks dreamlax
Added VS2012 project file. Thanks Glen Parker
[#35] Fixed array handling with prepared statements. Thanks Chen Huajun.
[#33] [#1011346] BUGFIX: Thread synchronization inside GetPooledConnector
[#57] Bytea handling optimizations. Thanks Rungee
[#59] Bytea decoder optimizations. Thanks Glen Parker
[#1000515] Prepare() makes command very slow. Thanks Glen Parker for optimizations.
[#61] Async notification optimizations and fixes. Glen Parker
[#63] [#1011334] NpgsqlConnection.GetSchema doesn't dispose connections
[#69] Fix extra-float-digits setup for postgresql below 9.0
[#92] Added InvariantCulture to NpgsqlCopySerializer. Thanks djsubzero
[#86] Rewrite query parameter substitution. Thanks Glen Parker
[#118] Detection of Parameter Direction in DeriveParameters method. Thanks Noé Garcia and Shay Rojansky
[#1011271] NpgsqlSchema: Use InvariantCulture on all return DataTables with schema data. Thanks Oskar Berggren for patch.
[#1011305] Scope without prepared transactions. Thanks Shay Rojansky for the patch.
[#1011310] Command timeouts after the first are not handled. Thanks Evan Martin for the patch.
[#1011316] ConnectionTimeout fix, bypass the 2147 seconds limit of Socket.Poll method. Thanks Tasos Mamaloukos for patch.
[#1011325] Escaped strings don't work with EF. Thanks Andrey Polyakov for patch and tests.
Implements DateTime canonical functions for EntityFramework. Thanks Andrey Polyakov for patch.
[#1011325] Escaped strings don't work with EF. Thanks Andrey Polyakov for patch and tests.
[#1011321] Wrong BitString value. Thanks Jon Hanna for patch and support.
[#1011326] Connection pooling timer (thus thread) is active even if connection pooling is disabled. Thanks Shay Rojansky for the patch.
[#1011001] Bug in NpgsqlConnectionStringBuilder affects on cache and connection pool. Thanks Shay Rojansky for the patch.
[#1011267] Monetary localization bug
[#1011085] Money format is not set in accordance with the system locale format

New features:

Add support for new error fields added in PostgreSQL 9.3. See here for more information about those fields: http://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=991f3e5ab3f8196d18d5b313c81a5f744f3baaea Thanks David Rowley for patch.

Initial support for Entity Framework 6. See http://fxjr.blogspot.com/2013/06/initial-ef-6-support-added-to-npgsql.html for more information about it.

[#30] Improved connection timeout handling. Thanks Glen Parker.

[#41], [#52], [#77], [#72], [#80] Huge internal query handling which added a big performance boost for prepared statements and unprepared statements as well. Binary parameter codec infrastructure has been added, and several data types (currently bytea, text, boolean, integers, and gloats) can now use PG's binary coded support, including arrays of those types, which offers a dramatic performance boost for parameter and result values in prepared statements. Previously we didn't recommend using prepared statements with Npgsql, only for bytea data types. Thanks to Glen Parker, this is now a thing of the past.

Huge directory and project structure. Npgsql had its project layout restructured to easy management of different platforms Npgsql targets: .net 2.0, 3.5, 4.0, 4.5, entity framework prior 6.0, entity framework after 6.0. Huge structure changes to our testsuite. Before, our tests depended on an external script to setup database tables, now everything is done inside the tests setup. Thanks Shay Rojansky.

[#74] Use new "Discard all" syntax when releasing connection from pool. Thanks Chen Huajun.

New connection string parameter "AlwaysPrepare" to indicate to Npgsql to always prepare statements before executing.

[#110] Added support for Entity Framework before version 6.0 and after 6.0. They are totally different things regarding APIs and namespaces. Thanks Shay Rojansky and Kenji Uno.

Added nuget EFProvider installation. Thanks Shay Rojansky.

Added EF6 ConnectionFactory class. Thanks Shay Rojansky.

[#135] Fix for operators @@, @> and <@. Thanks Glen Parker and jjchiw.

[#117] Command timeout improvements. Thanks Glen Parker.

Final considerations:

This release wouldn't be possible without the help of two members: Glen Parker and Shay Rojansky.

Glen Parker has been working in the optimizations tasks since his first git commit. He is an optimization machine! From the changelog you can see his tireless work regarding each part of Npgsql which could be optimized. Thank you very much for your contributions, Glen!

Shay Rojansky has been helping as the mastermind of the project restructuring support. He contributed a lot of changes which made our lives working with Npgsql much better. Thanks to him we can compile Npgsql for different .net platform versions easily. He also got TeamCity build server working as well as github integration. He helped us to get EntityFramework pre-6 and pos-6 verions easily integrated. Thank you, Shay!

I also would like to thank Dave Page who helped us with the server where the TeamCity is installed. Without his help, I'm sure our TeamCity installation would be much more difficult. Thank you, Dave!

Bugfix: Boolean constants converted to ETRUE and EFALSE instead of TRUE and FALSE.
Thanks [email protected]. Fix cherry-picked from Master.

This is a small bugfix release for 2.0.14 with fix for missing EF provider manifest.

This is a small bugfix release with fix for hangs which could happen when connecting to Postgresql 9.3.

This bug appeared when Postgresql sent an error message. Npgsql had a problem handling some error code fields and then hang while processing it. Whooops! :)

Thanks to Glen Parker, it is fixed on github https://github.com/glenebob/Npgsql2/commit/5800eec287fc72ee4d051750b05253aed8deb46e. If you are having hang problems while using Npgsql after upgrading the server to 9.3 version, this version is for you.

This is the 2.0.13-beta1 release