Francisco Figueiredo Jr Activities

Hi, all... On monday, I went to doctor to see about my fingers which were hurting very much... :( Of course, I had some type of RSI - Repetitive Strains Injuries . :( He said I would need to stay away from keyboards from some time, so, Npgsql2 release may take some more time than this week as I wanted. I hope to get everything done, but more slowly... :( Hiroshi also remembered me that our documentation is lacking information about Npgsql2. We need to fix that too. That's it guys. As soon as I have any news, I will let you know. Thank you!

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.

UPDATE : Thomas Burkhart sent me a mail telling me that this configuration syntax doesn't work on ms.net 2.0. This is the version which works: <?xml version="1.0" encoding="iso-8859-1" ?> <configuration> <system.data> <DbProviderFactories> <add name="Npgsql Data Provider" invariant="Npgsql" support="FF" description=".Net Framework Data Provider for Postgresql Server" type="Npgsql.NpgsqlFactory, Npgsql, Version=1.0.0.0, Culture=neutral, PublicKeyToken=5d8b90d52f46fda7" /> </DbProviderFactories> </system.data> </configuration> Thomas said that "the tags are case sensitive and the must be outside any <applicationSettings>" Thank you Thomas for your feedback which, for sure will help others to get their configuration up and running. I will check with Mono guys to see why my original configuration worked. Hi all! Today I committed an initial support for...

Hi all, We already started to work on Npgsql2 with support for .net 2.0 and ado.net 2.0. Josh Cooley already refactored all Npgsql classes to extend from .net 2.0 classes, like DbCommand, DbConnection and others. We hope to have a preview release soon with some long awaited features like Provider Factory support, design time in vs.net 2005 and others. Stay tuned!

Hi all! I'm really happy to announce that Npgsql Team has released Npgsql 1.0 final! I started to work on Npgsql 4 years ago, just after I finished my CS graduation course. What motivated me was the possibility to implement a network communication protocol and to have something done to community. I'm a big fan of OpenSource philosophy, better, I'm passionate about OpenSource and community, and realized I didn't return anything to it up to now. Besides that, I wanted to make part of it. So, I started sending a message to postgresql mailling list asking if there was something about that being worked on. I received some replies about nothing being done yet and one saying that a p/invoke based proof of concept was tested. I wanted to implement postgresql communication protocol so I started to work on it. Some time later, I sent another message talking about project launch. At that time, Dave Page, from pgAdmin, jumped the wagon and started to help me get project going. I ...

Hi all, Npgsql 1.0 RC3 is released! Download it here This release fixes some critical bugs with concurrent connection stablishment and "This stream does not support seek operation" error when sending a query. Please, have a look at release notes here for more information about there errors. We are almost finished with 1.0. We hope to have a 1.0 final really soon so we can get 100% concentration on ado.net 2.0 features.

Hi all, These past 10 days, Josh Cooley fixed and helped to fix a lot of critical bugs on Npgsql! Here are they: Josh Cooley fixed a bug when dealing with concurrent connection establishment using Npgsql RC2. When I implemented ConnectionTimeout support for connection establishment, I was incorrectly using an instance variable with a singleton object :( This was leading to some nasty problems like this . Here is the relevant stack trace: Npgsql.NpgsqlException: Operation not allowed on non-connected sockets. at Npgsql.NpgsqlClosedState.Open(NpgsqlConnector context) at Npgsql.NpgsqlConnector.Open() at Npgsql.NpgsqlConnectorPool.GetNonPooledConnector(NpgsqlConnection Connection) at Npgsql.NpgsqlConnectorPool.RequestConnector(NpgsqlConnection Connection) at Npgsql.NpgsqlConnection.Open() Another problem, this time with async notification support, was that Npgsql wasn't handling correctly the notification message sent from server when async notification was off. This was le...