epgsql development has picked up steam in the past few days with changes to support some of the upcoming features of PostgreSQL 9.0, bug fixes, and support for delivering asynchronous notices and notifications from the LISTEN/NOTIFY mechanism which will be much improved in PostgreSQL 9.0.
I've also moved development to GitHub since git has become my primary version control system. You'll find the new master repository here:
http://github.com/wg/epgsql
The old mercurial repositories will no longer be updated, but I'll leave them up for the time being. If you're a mercurial user please accept my apologies. I'm a big fan of hg but maintaining two repositories would be too much work, and git has a few killer features that convinced me to switch.
4 comments:
Hi Will,
would be nice to have the epgsql_pool code moved to github as well so everything is centralized in one point.
I guess it has'nt change for a while since the code is pretty small.
Cheers, Sebastien.
Could you say something about the killer features of git over and above hg?
I'd also like to hear which features convinced you to switch.
seb3s: I'm not maintaining epgsql_pool as I don't think connection pooling is the right approach for Erlang. Instead I tend to pool db accessor processes which each have their own connection, which cuts down on the overhead of leasing connections to new owners. If you want to use it, zotonic has a version with some bug fixes.
Zteve and Brandon: I much prefer git's branching model and like to keep my commit history clean with judicious use of rebase.
Post a Comment