[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Gnumed-devel] gmObject problem
From: |
Horst Herb |
Subject: |
Re: [Gnumed-devel] gmObject problem |
Date: |
Sat, 26 Oct 2002 15:31:16 +1000 |
User-agent: |
KMail/1.4.7 |
On Sat, 26 Oct 2002 14:21, Horst Herb wrote:
> The big problem is:
> If such an object would be part of an outer transaction (invisible to this
Possible solution:
Instead of always passing a connection broker to the constructor of pgobject,
we could pass a tuple (open read-only connection, open read-write connection)
to the constructor.
Then, by checking the type of the parameter, the object could initialize
itself accordingly.
If it is part of a larger outer transaction, the open write connection is used
and thus final comittment would depend on the outer transaction.
Sounds simple enough to implement, can anybody see any major drawbacks (other
than needing to know the transactional level at the time we create an
object)?
Horst