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

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