On 7/19/05, David H [EMAIL PROTECTED] wrote:
Hi list,
At times (it seems) necessary to force a Zope transaction commit. This
might occur between two zSQL calls where the second depends on the
first's *SQL* transaction's availability but the first has not yet been
commited because the
Bakhtiar A Hamid wrote:
On 7/19/05, David H [EMAIL PROTECTED] wrote:
Hi list,
At times (it seems) necessary to force a Zope transaction commit. This
might occur between two zSQL calls where the second depends on the
first's *SQL* transaction's availability but the first has not
It would be better if you explain what you're trying to obtain. Inside a
single *Zope* transaction, all the queries are inside the same *RDBMS*
transaction.
Therefore, the second sql method should see the effects of the first
one. If that is not the case, review what is actually happening (i.e.
Am Dienstag, den 19.07.2005, 00:35 -0700 schrieb David H:
...
Your idea is what I thought of at first - but my Interbase Adapter
doesn't like COMMIT statements (!) and I didn't test it out. But it
seems that would not solve the problem because both ZSQL methods are
embedded in the *same*
