Subject | ISAPI and IB_Transaction |
---|---|
Author | henkfung |
Post date | 2003-10-03T15:07:39Z |
Hi,
I would appreciate it very much if someone could clarify the
following for me on ISAPI and IBObjects or point me in the right
direction.
I have an ISAPI application developed in D7 using Web Broker with:
1. TIB_Cursor for displaying the data.
2. TIB_DSQL for updating the database.
I read the following in the Online FAQ on ibobjects.com:
"If there is only one transaction component on the data module, will
the > IB_Transaction on components use that transaction?
No, > means that it will create its own internal transaction. You must
deliberately set a component's IB_Transaction property to your
transaction component, by selecting it from the drop-down list. This
is preferable to letting IBO create its own transaction, especially
in an ISAPI module.
Also, placing transaction components on a data module is not
recommended for ISAPI."
I am at lost here. From "This is preferable to letting IBO create its
own transaction, especially in an ISAPI module." I understand that is
preferable to explicitly set the IB_Transaction property. But in the
next sentence the advice is given not to put transaction components
on the data module (web module)?
My questions are:
1. Do I use an IB_Transaction component or not. If not, why shouldn't
an IB_Transaction component placed on the Web Module.
2. Is TIB_DSQL.Execute enough for an UPDATE or INSERT to be committed
to the database if an IB_Transaction component is not placed on the
Web Module.
Thanks for any input.
Henk
I would appreciate it very much if someone could clarify the
following for me on ISAPI and IBObjects or point me in the right
direction.
I have an ISAPI application developed in D7 using Web Broker with:
1. TIB_Cursor for displaying the data.
2. TIB_DSQL for updating the database.
I read the following in the Online FAQ on ibobjects.com:
"If there is only one transaction component on the data module, will
the > IB_Transaction on components use that transaction?
No, > means that it will create its own internal transaction. You must
deliberately set a component's IB_Transaction property to your
transaction component, by selecting it from the drop-down list. This
is preferable to letting IBO create its own transaction, especially
in an ISAPI module.
Also, placing transaction components on a data module is not
recommended for ISAPI."
I am at lost here. From "This is preferable to letting IBO create its
own transaction, especially in an ISAPI module." I understand that is
preferable to explicitly set the IB_Transaction property. But in the
next sentence the advice is given not to put transaction components
on the data module (web module)?
My questions are:
1. Do I use an IB_Transaction component or not. If not, why shouldn't
an IB_Transaction component placed on the Web Module.
2. Is TIB_DSQL.Execute enough for an UPDATE or INSERT to be committed
to the database if an IB_Transaction component is not placed on the
Web Module.
Thanks for any input.
Henk