Skip to main content

Npgsql 2.0.11 released!

As I've said in my last post,  Npgsql 2.0.11 is finally here!

This release fixes the problem with bytea handling with Postgresql 9.0. This patch should have been applied a long time ago. My fault for not being there yet.

Also on this release, Josh Cooley fixed some other bugs related to EF.

Checkout the release notes here for more info and download it from here.

Comments

conan said…
"Il Pelagos è diventato il mio orologio da cucina per eccellenza. È così dannatamente duro e, ai miei occhi,replica rolex sembra un po 'meglio con la patina dell'usura. Gli orologi da strumento dovrebbero essere curati, ma non nascosti", ha detto Gillespie. Ma non si è fermato qui. In effetti, ha un po 'di più per l'orologio che individua la folla su cui affondare i denti. "Continua a guardare e vedrai che,orologi replica più avanti nella stagione, passerò al Panerai Luminor Titanium su un cinturino in gomma."

Popular posts from this blog

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

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

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