Skip to main content

Array support in the works!

Hi all,

Jon Hanna is working to add Array support to Npgsql. He already sent a patch which I applied to my working copy and it is working very well!

Now it is possible to write code like that:

NpgsqlConnection conn = new NpgsqlConnection("Server=127.0.0.1;User id=npgsql_tests;password=npgsql_tests;");

conn.Open();

NpgsqlCommand d = new NpgsqlCommand();

Int32[] a = new Int32[2];

a[0] = 4;
a[1] = 2;

NpgsqlCommand command = new NpgsqlCommand("select :arrayParam", conn);

command.Parameters.Add(new NpgsqlParameter("arrayParam", a));
Console.WriteLine(command.ExecuteScalar());

conn.Close();

And get this logged on server:

LOG: statement: select array['4','2']::int4[]

Also, Npgsql is able to receive an array from server as the example above shows. Npgsql will print to console:

System.Int32[]

Which shows it received an int32 array as expected!

Excellent work, Jon!

Comments

Anonymous said…
Thanks for the kind words on the patch.

One thing worth adding is that since .NET2.0 has several different types of typed collection as well as arrays these can be used too:

Anything that implements IEnumerable<T> where T is a type already supported by npgsql will be treated the same as T[], anything that implements IEnumerable<U> where U implements IEnumerable<T> will be treated the same as T[,] (but cause an error if it's a "jagged" array, as postgres doesn't support them) and so on.

So, List<int> will be treated as a Postgres int4[], ICollection<List<string>> as a two-dimensional text[] and so on.

However, we look for direct support first, so string is still treated as string rather than as IEnumerable<char>, unless you explicitly ask for that.

Michael Parshin did a good job at catching a couple of edge cases in my previous attempt here.
02 February, 2008 20:08
Post a Comment

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 complain with the followin...
45 comments
Read more

Fixed! LOG: unexpected EOF on client connection

Hi all! Since we implemented connection pool in Npgsql, we received some complaints about EOF log messages being generated on Postgresql logs when using Npgsql. This was caused by Npgsql not sending the proper terminate message to Postgresql on pooled connections when the application terminated or more specifically when the assembly was unloaded. This is a long time problem with Npgsql connection pool. I even talked about it in the past . Up to now, I had no idea about how to fix that as I wasn't able to close the connections in the pool. When I tried to put a finalizer in NpgsqlConnectorPool, which would be triggered when the assembly was unloaded, I received object already disposed exceptions when trying to send something to the stream. That's when I came up with the "excellent" idea of subclassing the networkstream class and override its Dispose method so that I could send the postgresql terminate message before it was disposed! :) It worked like a charm! ...
5 comments
Read more

Npgsql 2.2.0 final release is out!

This is Npgsql 2.2.0 Final Release 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. E...
15 comments
Read more