Skip to main content

Posts

Showing posts from August, 2010

Npgsql receives donation of an MSDN subscription!!

Hi all! It all started when Josh Cooley told me about this post:  http://devlicio.us/blogs/tuna_toksoz/archive/2010/07/27/codebetter-devlicio-us-msdn-ultimate-giveaways.aspx I sent a mail talking about Npgsql and how a VS.Net would help us to add design time support and today I received a very nice mail saying that Npgsql was choosen to receive an MSDN subscription! I'd like to thank the people who contributed to make this possible: Codebetter Crew : Ben Hall , Ward Bell , James Kovacs . Devlicious Crew : Hadi Hariri , Christopher Bennage , Tim Barcz , Rob Reynolds .  Lostechies Crew : Eric Hexter , Jimmy Bogard , Keith Dahlby and Josh Cooley for heads up! Thank you very much! Your support to OSS projects is awesome! And stay tuned for better support of Npgsql inside VS.Net :)

New Android Blog

Hi all! I've been playing with Android for quite some time now and so I decided to create a blog where I'll talk about my experience with the platform and the projects I'm developing for it. The blog page is: http://franciscodroid.blogspot.com I invite you all who are interested in the platform to have a look at it. This blog will continue to be about Npgsql, Mono and other relevant things. I decided to create another blog so I could concentrate posts about Android there. Feedback, as always, is very welcome.

Npgsql 2.0.10 and NpgsqlParameter.Value

Hi all! As you may already know, Npgsql 2.0.10 is out . Besides the usual batch of bug fixes and enhancements, this release has a new feature which needs more attention as it may give you backward compatibility problems. What happened? With this release, we decided to implement a property in NpgsqlParameter which returns provider specific objects, just like SQLClient does. NpgsqlParameter now features a property called NpgsqlValue. As you may guess, when you use it, you will receive a value whose type is Npgsql specific. Why this change? In the past, we had a lot of problems dealing how we would handle values which are specific to Npgsql, like NpgsqlTimestamp from others which are represented in CLR, like DateTime. This situation led to cast exceptions bugs . This was the main motivation for this. Also, we think that by implementing this we would be giving our users a much consistent way of getting values in CLR type and in Npgsql-specific type. Another benefit is that now Npgsql can ...