Subject | Current_Time / Current_Date / Commit |
---|---|
Author | focusedpoint <focused1@optushome.com.au> |
Post date | 2003-02-07T00:47:17Z |
Hi all
Using FB1.02
I have a group of stored procedures which perform a rather lengthy
sequence of calculations and subsequent table inserts. These
operations
are logged at various intervals in a separate table.
The problem I'm having is that the date and time logged for each
entry
(which is assigned using current_date and current_time) is the same
for
every log entry with a single calculation run, even though the run
takes
a few minutes to complete. I am therefore assuming that the date and
time are assigned when the transactions are finally commited. Is
that
correct? If so, is there some way I can get the transacations
commited
at nominated points instead of just when the operation finally
completes? It seems that 'commit' is not a valid keyword inside
stored
procedures.
Thanks
Paul Turner
Using FB1.02
I have a group of stored procedures which perform a rather lengthy
sequence of calculations and subsequent table inserts. These
operations
are logged at various intervals in a separate table.
The problem I'm having is that the date and time logged for each
entry
(which is assigned using current_date and current_time) is the same
for
every log entry with a single calculation run, even though the run
takes
a few minutes to complete. I am therefore assuming that the date and
time are assigned when the transactions are finally commited. Is
that
correct? If so, is there some way I can get the transacations
commited
at nominated points instead of just when the operation finally
completes? It seems that 'commit' is not a valid keyword inside
stored
procedures.
Thanks
Paul Turner