Can we agree on this: 1) migrate to psycopg2
Why ? - actively maintained/developed - lets us avoid mx.DateTime - offers connection pooling (reduce gmPG complexity) - has more unit tests now - offers async queries - offers access to SQLSTATE error codes 2) use SQLSTATE based error handling - do not rely on textual (possibly i18ned) error messages 3) implement Ian's concept of exception-throwing business objects - drop SELECT FOR UPDATE but - use XMIN in update operations in - serialized transactions Karsten -- GPG key ID E4071346 @ wwwkeys.pgp.net E167 67FD A291 2BEA 73BD 4537 78B9 A9F9 E407 1346 _______________________________________________ Gnumed-devel mailing list [email protected] http://lists.gnu.org/mailman/listinfo/gnumed-devel
