Hello Olaf

When you insert/delete/update a record (row) in a table it is only visible
to the current transaction. Others transactions can not see the changes
until a COMMIT is executed.

You can use POST_EVENT to say them that a COMMIT was executed and so they
can refresh their data and see the new values.

Greetings.

Walter.

On Fri, May 6, 2011 at 6:04 PM, Olaf Kluge <olaf.kluge@...> wrote:

>
>
>
>
> Hello,
>
>
> On Fri, May 6, 2011 at 5:29 PM, Olaf Kluge <olaf.kluge@...
> <mailto:olaf.kluge%40satron.de> > wrote:
> >
> > How can I insert data in more than one table and commit both the same
> time?
> > Both tables should have the new data at the same time.
> >
> > In procedures I don't know a command like "commit" or "rollback". We are
> > using firebird 2.5 for this project.
> >
>
> You issue the commit or rollback in the client application, or use execute
> 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.
>
> Thanks.
>
>
> Olaf
>
> [Non-text portions of this message have been removed]
>
>
>


[Non-text portions of this message have been removed]