Skip to main content

Npgsql 2.2.0 beta1 released!

The Npgsql Development team is proud to announce that Npgsql 2.2.0 beta1 is now available!

This release has the following 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.


Support for EFMigration and Database creation in EF6+

David Karlaš added support for that. 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.

Check out this list containing fixes from David and Emil as well as others for EntityFramework.

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



Complete release notes for this release can be found on our github release page.


Downloads

Downloads are available on Nuget, github and pgfoundry.

Please, give it a try and let us know what you think. Drop by our user forums to discuss or send your bug reports to our issues section on github.
Labels:

Comments

nbde2020 said…
All diese Steine sorgen auch für audemars piguet replica eine Menge Augenweide - und auch dafür, dass etwas schief geht. Die Lünette mit ihren Saphiren im Baguetteschliff steht replica uhren in einem angemessenen rolex replica Verhältnis zum Gehäuse und zur Uhr insgesamt, und das ist großartig. Die Laschen und die Zifferblattkomponenten sehen jedoch außerordentlich panerai replica seltsam aus, als gehörten diese kleinen Steine ursprünglich zu einer Michael Kors-Modeuhr, nicht zu einem sechsstelligen Stück - obwohl die Qualität der Einstellungen und der Schnitte natürlich stimmt hublot replica gehören zum Luxussegment.

Alles, was bemerkt wird, diese Uhr für IWC replica die unverhältnismäßigen Steine und den resultierenden Gesamtblick zu kritisieren, ist wie ein Maskenbildner, der auf einen Clown cartier replica uhren zugeht und die Nuancen seines Make-ups kritisiert. Es fehlt eindeutig der Punkt und das ist etwas, was ich nicht tag heuer replica tun möchte. Also, hier ist, was ich zum Schluss sagen werde.

High-end fashion classic replica watches, worth collecting.www.vipwatches.co
16 December, 2019 05:05
Post a Comment

Popular posts from this blog

UUID datatype and COPY IN/OUT support added to cvs

Hi all! It was just added support to uuid datatype in cvs head. This type will be available in next Postgresql release 8.3. Thanks to David Bachmann for his patch! You can get more info about this patch in this mailing list post . Also was added support for copy in and copy out operations. Now, users can provide streams which can be copied directly to and from Postgresql tables! Thanks to Kalle Hallivuori for providing a patch! Thanks to Truviso for giving support to Kalle. More info about that including a demo and ready to use compiled Npgsql.dll versions can be found here . That's it! As soon as we get more features added, I will post info about them here. Stay tuned! :)
1 comment
Read more

Npgsql Tips: Using " in (...)" queries with parameters list and "any" operator

Hi, all! We have received some users questions about how to send a list of values to be used in queries using the "in" operator. Something like: select foo, bar from table where foo in (blah1, blah2, blah3); Npgsql supports array-like parameter values and the first idea to have this working would try to use it directly: NpgsqlCommand command = new NpgsqlCommand("select * from tablee where field_serial in (:parameterlist)", conn); ArrayList l = new ArrayList(); l.Add(5); l.Add(6); command.Parameters.Add(new NpgsqlParameter("parameterlist", NpgsqlDbType.Array | NpgsqlDbType.Integer)); command.Parameters[0].Value = l.ToArray(); NpgsqlDataReader dr = command.ExecuteReader(); but unfortunately this won't work as expected. Npgsql will send a query like this: select * from tablee where field_serial in ((array[5,6])::int4[]) And Postgresql will complain with the followin...
45 comments
Read more

Using Entity Framework 6 with Npgsql 2.1.0

UPDATE (2014-05-19): Marek Beneš noticed a problem in the default connection factory config. It is fixed now. Thanks, Marek! UPDATE (2014-02-20): I created a new post explaining how to get Npgsql 2.1.0. Although this post is about EF 6, I'd like to talk about our current situation to support both EF 6 and EF4.x which explain why there are some subtle changes between EF 4.x and EF 6.x App.config settings.  Support for EF versions 4.x and 6.x Sometime after we started to work on Npgsql 2.1.0, we started to add code to support EF6 and decided to reorganize our Entity Framework support code. Shay created a pull request to organize this change and isolate the EF code out of core Npgsql code. The result was the creation of two separated assemblies: Npgsql.EntityFramework.dll for EF6 and above; Npgsql.EntityFrameworkLegacy.dll for EF4.x. Only when using Npgsql with EF6 you will need to reference Npgsql.EntityFramework.dll assembly. This is needed because the EF ...
26 comments
Read more