Npgsql can be found on GitHub at the following addresses: Thank you guys!Īnd last but not the least, I'd like to thank people from pgfoundry where Npgsql had its code hosted until now. This script did all the hard work of converting the code from cvs to git. Thank you very much, Shay!Īlso, I'd like to thank the persons behind the excellent script cvs2git. Shay has been helping me since the beginning and gave me all the support I needed to get Npgsql code into GitHub. I'm sure that, without his help, this migration would have taken a lot more time: Shay Rojansky.
I'd like to thank a person who contributed a lot to make this happen. I hope you enjoy this change as much as I do. I'm very confident this change will bring a lot of benefits to Npgsql community.
This will allow users who want to test an unreleased version of Npgsql to try out new features without having to either install git or wait for us to create a beta version. GitHub provides links to download code from each branch. Besides that, our collaborators will be able to use all the power of git to get a better workflow when playing with Npgsql code. We will be able to much easily apply changes from our collaborators based on those pull requests. GitHub provides many resources which will help us have a much better environment for our collaborators and users.įor our collaborators there is the idea of cloned repositories and the ability to give us a much better feedback based on pull requests. Git was chosen mainly because there is a lot of documentation about it, it is powerful and because of GitHub.
Every change had to go first to the main repository cvs and then I would update in GitHub. And I had to update the code manually every time. But it was only a mirror of the main cvs repository. :) ( You may be asking yourself: But Npgsql code was already at GitHub, wasn't it? Yes, it was. I didn't blog about that in the same day because I wanted to make sure things went well before spreading the word.
Nathaniel Manista is a graduate of Carnegie-Mellon University and has worked as a software engineer since 2004.A couple of days ago, Npgsql code moved to GitHub. When not in front of a computer, he enjoys playing the french horn in community ensembles. Augie lives in Pittsburgh and works at Google's Pittsburgh office where he maintains Mercurial-on-BigTable for the Project Hosting team. He has a Bachelor of Science degree in computational mathematics from Hillsdale College. He also started the Perian project and contributed to Adium. We will conclude with the last and best of these techniques: a new modularity for the design of our software.Īugie Fackler is the author of many Mercurial extensions including hgsubversion, maintainer of hg-git, and contributor to Mercurial.
We will present superior techniques we use in place of inheritance that have made our programs easier to understand, use, extend, and maintain. We?ll explain how inheritance obfuscates our code and requires sympathetic co-obfuscation of the code of our clients. The End of Object Inheritance & The Beginning of a New Modulariy BookmarkedĪfter 15 years of combined experience developing software of all types we are done with inheritance. But, thanks to Josh Cooley and Jerónimo Milea who posted a solution on our forum, you just have to change your 'in' operator to use the 'any' operator and it will work as expected: NpgsqlCommand command new NpgsqlCommand ('select from tablee where fieldserial any (:parameterlist)', conn) So if you want to use a query to compare a list.