Subject | Sorry, but I got lost again (about transaction) |
---|---|
Author | James Chua |
Post date | 2003-12-04T02:48:28Z |
Today I have learn that savepoint and lose point is not the thing that I
want.
For example I have two ib_query in the same form. In both ib_query I
have some newly insert records but not yet committed. Before I do
something like ib_query1.ib_transaction.savepoint, to commit all the
things that I have done in the ib_query1. But I recently found out that
doing this commits also my work in ib_query2 which I don't want to
commit it yet. Is there a way for what I want it to be? Before in IBX I
use to have this kind of feature.
As for now I only think of dropping another ib_transaction and assign a
different ib_transaction to each ib_query, other than that do I have
other way?
Thanks for your help!
James
want.
For example I have two ib_query in the same form. In both ib_query I
have some newly insert records but not yet committed. Before I do
something like ib_query1.ib_transaction.savepoint, to commit all the
things that I have done in the ib_query1. But I recently found out that
doing this commits also my work in ib_query2 which I don't want to
commit it yet. Is there a way for what I want it to be? Before in IBX I
use to have this kind of feature.
As for now I only think of dropping another ib_transaction and assign a
different ib_transaction to each ib_query, other than that do I have
other way?
Thanks for your help!
James