Subject | AW: [firebird-support] transaction |
---|---|
Author | Olaf Kluge |
Post date | 2011-05-06T22:20:21Z |
Hello,
On Fri, May 6, 2011 at 5:29 PM, Olaf Kluge < <mailto:olaf.kluge%40satron.de>
olaf.kluge@...
<mailto:olaf.kluge%40satron.de> > wrote:
statement to construct a commit inside a procedure. Procedures do not
normally include commit or rollback statements by design, because the
model is that the client determines the fate of changes. Having client-side
operations committed or rolled-back as a side-effect of running a procedure
makes it harder to develop reliable applications.
Good luck,
Ann
Thank you. I mean the commit in a stored procedure.
We have a new project. I should insert some values in more tables and the
client like to see the data in all tables to the same time. We are the LVS,
our partner is the ERP.
How handle this part a procedure? I think, at the moment I insert a new
record in a table, at this moment the record is visible and committed, or
not? But our wish is to show the record first until all data written.
Oh, I should say, the a trigger calls the procedure, not an external
application.
Thanks.
Olaf
[Non-text portions of this message have been removed]
On Fri, May 6, 2011 at 5:29 PM, Olaf Kluge < <mailto:olaf.kluge%40satron.de>
olaf.kluge@...
<mailto:olaf.kluge%40satron.de> > wrote:
>time?
> How can I insert data in more than one table and commit both the same
> Both tables should have the new data at the same time.You issue the commit or rollback in the client application, or use execute
>
> In procedures I don't know a command like "commit" or "rollback". We are
> using firebird 2.5 for this project.
>
statement to construct a commit inside a procedure. Procedures do not
normally include commit or rollback statements by design, because the
model is that the client determines the fate of changes. Having client-side
operations committed or rolled-back as a side-effect of running a procedure
makes it harder to develop reliable applications.
Good luck,
Ann
Thank you. I mean the commit in a stored procedure.
We have a new project. I should insert some values in more tables and the
client like to see the data in all tables to the same time. We are the LVS,
our partner is the ERP.
How handle this part a procedure? I think, at the moment I insert a new
record in a table, at this moment the record is visible and committed, or
not? But our wish is to show the record first until all data written.
Oh, I should say, the a trigger calls the procedure, not an external
application.
Thanks.
Olaf
[Non-text portions of this message have been removed]