M.-A. Lemburg wrote at 2008-1-22 13:42 +0100: > ... >We could just describe the transaction id as object in the spec and >then have the modules decide what type this maps to, e.g. one module >might want to use a tuple (or even namedtuple) for this, another >might not want to bother at all and use the internal representation >mapped to a string or bytes object.
I learned (from James remark) that transaction ids belong to the transaction manager and not the resource. Thus, at least the individual "drivers" should not use different implementations for transaction ids. -- Dieter _______________________________________________ DB-SIG maillist - DB-SIG@python.org http://mail.python.org/mailman/listinfo/db-sig
