Skip to main content

Npgsql is still alive! And license change in works...

Hi, all!!

It's been a long time since my last post.

I apologize for that. :(

Since end of last year I had a lot of personal problems and I also was studying for some job tests which took a lot of my time and I couldn't work very much on Npgsql.

But now I think things are settling and I'm getting more time to work on Npgsql! :)

Right now, we are working in the process of change Npgsql license from LGPL to BSD. We believe this change would allows better integration of projects (commercial or not) and we will have the same license as postgresql server itself.

I'm revising our code and asking people who commited any code to Npgsql his authorization to relicense their patches.

So, if you submitted any patch to Npgsql and didn't receive a mail from me asking your authorization, please, send a mail.

I will come back later with more details about it.

Thank you very much for your feedback and patience.

Comments

This comment has been removed by the author.
Anonymous said…
I wrote Francisco - if there is anyone willing to help out on the project, especially if you have worked on it before - or have worked with Francisco before...

I am willing to fund some of the development. Something in the USD$1,500 to start with... any developers interested to work on it for 30 or 40 days full time if funded?

My name is Stephen, I suggest you contact Francisco if you are interested - he can contact me.

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

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

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