Commit TUniTransaction before closing TUniTable

[testpresta]

Hello

I have several TUniTable components which property transaction is set to an unique TUniTransaction.

I start transaction before opening any table.
Then, i close some tables before commit transaction and i close other tables after commit transaction.
(same thing for rollback).

Does it works properly this way ?

Thanks

[azyk]

We don't fully understand the point of your question. If you have encountered a problem in a particular case, please describe it in more details.

[testpresta]

Everything works but i want to know what is the best practice:

- I open TUniTable
- I start a TUniTransaction that is associate to the previous TUniTable
- I append or edit TUniTable then post
- I close the TUniTable component (close method)
- I commit transaction

or

- I open TUniTable
- I start a TUniTransaction that is associate to the previous TUniTable
- I append or edit TUniTable then post
- I commit transaction
- I close the TUniTable component (close method)

[azyk]

We can not give a definite answer to such a general question. You should choose a transaction control logic depending on the business logic of your application and the used DBMS.