Currently there is no specification to describe the SQL statement interface transaction boundaries.
Consideration needs to be given to how these boundaries should be handled by
default (starting a SQL statement i/f method is called; and ending when the
method returns). Applications may also want to control these boundaries, in paricular setting Savepoints and in batching environments.
Note: you can never *exactly* know when the transaction boundary is reached. There is *always* some lantency.
###@###.### 2004-11-12 02:18:09 GMT
###@###.### 2004-12-10 23:17:25 GMT
Consideration needs to be given to how these boundaries should be handled by
default (starting a SQL statement i/f method is called; and ending when the
method returns). Applications may also want to control these boundaries, in paricular setting Savepoints and in batching environments.
Note: you can never *exactly* know when the transaction boundary is reached. There is *always* some lantency.
###@###.### 2004-11-12 02:18:09 GMT
###@###.### 2004-12-10 23:17:25 GMT