1-3 sound good.
4. I was thinking that TurbineUserPeer and possibly anywhere else (this
should be minimized) that is using the Visitor table should perform these
tasks.
Maybe a helper method in BasePeer or a Transaction class would be
appropriate?
John McNally
----- Original Message -----
From: Nissim <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, July 03, 2000 8:00 AM
Subject: Transactions
> I committed the transaction support stuff in BasePeer.
>
> This is what I think we should do for postgres support:
>
> 1) Add objectDataNeedsTrans method to abstract DB class (to return
> false).
> 2) Add objectDataNeedsTrans method to DBPostgres to return true.
> 3) Add boolean containsObjectColumn() to TableMap.java
> 4) in the BasePeer methods that return stuff from the db but don't take
> a connection argument, check first if objectDataNeedsTrans, then if
> that's true, check if any of the tables in the criteria
> containsObjectColumn, and if that's true, set up a transaction.
>
> Does anyone think that this is too much?
>
> -Nissim
>
>
> ------------------------------------------------------------
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
> Problems?: [EMAIL PROTECTED]
>
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
