hi all, yesterday i posted a fix for the turbine 2.1 release and postgres that uses bytea instead of oid to store OBJECTDATA. since the transaction is necessary for large objects in postgres, but not bytea, and other databases do not use a transaction for OBJECTDATA i changed my DBPostgres to return false for the "requires transaction" method for said transaction.
a person on the turbine-user list asked me why i did that. so, given what i just stated, should i try to justify my decision or just not worry about it? how will turbine 3 handle this issue? thanks, rhys -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
