Re: [PATCH] Re: DB (Postgres & Transactions, unresolved issues)

[Nissim]

I'm replying to this message because there's an additional issue I
didn't address with this patch.  Although the patch in the previous
message will work for postgres for the user stuff, it's not a general
solution to using tables which contain large objects in postgres.  So
when you start making peer classes for the attachment tables in scarab
(or any other tables containing binary data), you're going to have the
same problem again.

        -Nissim


Nissim wrote:
> 
> OK, it's done.  I came up with another solution for Postgres which
> requires minimal changes to existing classes: Make a new User class
> which extends TurbineUser for postgres (and one to extend
> TurbineUserPeer).  I also used the DBConnection as the transaction key,
> and not Connection because then the Commit and RollBack can easily
> release the DBConnection back to the pool.  Below are the patches to
> existing code, and the two new files can be found in a tgz archive at
> http://nissim.karpenstein.com/turbine_postgres.tgz ... I hope you all
> buy it this time :-)
> 
>         -Nissim
>


------------------------------------------------------------
To subscribe:        [EMAIL PROTECTED]
To unsubscribe:      [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?:           [EMAIL PROTECTED]