Devart Forums

Hi,

please what is the advantage of linking multiple TIBCTransaction components with a single TIBCConnection component ? For what situation is this intended ?
What advantages has the usage of multiple connections ?
Perhaps also what is the purpose of linking multiple TIBCConections with a single TIBCTransaction ?

This is a newbie question. Untill now I have used two transactions - one for read and one for write with different isolation levels.
Could I run more transactions independently when they are linked with a single connection ?

You can link several TIBCTransaction components to one TIBCConection component, to use independent parallel transactions with one connection. Set the Transaction or/and UpdateTransaction properties of TIBCQuery and TIBCSQL to the corresponding TIBCTransaction component. When you call the Commit method of TIBCTransaction component, only changes that are made through TIBCQuery and TIBCSQL components linked to this transaction is committed.

You also can create a distributed transaction by linking several TIBCConnection components to one TIBCTransaction component. This allows you to create a transaction on several databases. If an error occurs on committing the changes on one database, you can rollback all changes on all databases.

Thank you, Plash.
Please, are there situations where an application could need multiple connections to the same database ?

If there are several users in the database, an application could use multiple connections for different users. I think there is no sense to create multiple connections with identical parameters.

And for multiple threads of a single application ? Shouldn't each thread have own connection with identical parameters ?

Yes, it is recommended to use a separate connection for each thread.