What happens with a record that is being edited if all its fields are empty and I do CommitRetaining of a transaction? Can I continue editing this record or will I have problems ?
Fast, flexible and high-performance component library for Delphi, C++ Builder and Kylix intended for work with InterBase and Firebird using Direct InterBase API.
Question:
What happens with a record that is being edited if all its fields are
empty and I do CommitRetaining of a transaction? Can I continue editing
this record or will I have problems ?
When editing a record (i.e. customer), I need to add a new language
code or a new payment condition. If this is a problem, I’d
rather have a transaction per table with the exception of tables that
must be committed together (i.e. customer balance and customerdetail). Answer:
The CommitRetaining does not cancel or influence the current Insert of
the editable record.
So you can edit or insert a new record in one dialog window, switch to
another window, add or edit existing records, post them and do
CommitRetaining. Then switch to the primary window and you’ll
be able to use the new code. So it is not necessary to have a separate
transaction for each table, the read and write transactions are ok.
Waaaaw, what a difference in support with IBO, most of the time when I asked something there, I got a arrogant answer. This is really great and I must say, there is a significant difference in speed that FIBPlus is faster! >>
Nico Callewaert
FOR CUSTOMERS Download full versions and updates in our Customer's Center