Skip to main content

Npgsql 2.2.0 Release Candidate 1 released!

This release contains 22 commits since the last release. It contains 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: v2.2.0-beta1...release-2.2.0
Labels:

Comments

Unknown said…
Very interesting! Thanks you
Signature:
facebook entrar iniciar sesion gratis - Sitio Oficial iniciado sesión en Facebook lengua española. facebook entrar rápido, facebook iniciar sesion en tu cuenta de entrar facebook
06 August, 2015 06:04
Post a Comment

Popular posts from this blog

Npgsql Code First Entity Framework 4.3.1 Sample

After reading the excellent article about entity framework on Postgresql by Brice Lambson, I decided to write this post to document my experience playing with Entity Framework 4.3.1 and Npgsql. This post will be an adaptation of the Code First To a New Database walkthrough in order to make it work with Npgsql.  First Steps You should follow the first 4 steps of Code First To a New Database. Go ahead, I''l wait for you. Next steps Here is where the adaptation of the walkthrough begins. As Brice noted in his post, Npgsql currently doesn't support database creation. ( I'm working on that and hope to get news about it soon.) So, for while, you have to create the database manually. Those are the steps you have to do to create the database and the model: First, run this command in the terminal to create the database (or you can use pgAdmin if you prefer a GUI): > createdb ef_code_first_sample  After that, you have to run the following commands
14 comments
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 comp
74 comments
Read more

Happy 20th Anniversary, Npgsql!

      Happy 20th Anniversary, Npgsql!      It seems like yesterday when I decided to start Npgsql. And today, Npgsql completes 20 years since the first public beta release!     On May 18th, 2002, this is what was written in the first release notes of Npgsql  version 0.1:   2002-05-18          First Npgsql beta release.     In this version there is a limited functionality. It is only possible to connect and disconnect from server.     Only clear text authentication is supported right now.     To compile you can use the SharpDevelop to open the Combine file (Npgsql.cmbx) or type at command console: csc /t:library /out:Npgsql.dll NpgsqlConnection.cs AssemblyInfo.cs NpgsqlException.cs This will create the file Npgsql.dll that can be copied to the application directory.     I will be working in the Command functionality now.               Play with it and send your bugs and comments :)     (fxjr)           It's been a long journey since then. And what a journey!! :)     It all started
Post a Comment
Read more