Hi again,
Mark, thanks for answering.
In the meantime I've found the problem. It was caused by:
1) I've selected the current value of the generator for the ID.
2) the set of data was inserted in table_a (and the ID was increased a
second time by a trigger, aaaaaarrrrgggghhhh)
3) inserting the data in table_b was canceled, because of the wrong ID
sorry, it was my fault !
bye
----- Original Message -----
From: "Mark Thornber" <[EMAIL PROTECTED]>
To: "Gerd K�nig" <[EMAIL PROTECTED]>
Sent: Thursday, September 13, 2001 2:45 PM
Subject: Re: interbase and transactions
> Gerd,
>
> Stupid question ... but you _are_ adding the row to the primary key
> table before adding the row to the foreign key table ?
>
>
> --MarkT
>
> Gerd K�nig wrote:
>
> > Hi,
> >
> > I'm having problems with handling transactions from perl - interbase.
I'm
> > using DBD::InterBase.
> > Inside my perl script I execute 2 insert-statements on 2 different
tables
> > which are combined with referral integrity.
> > Between this 2 statements there are no commit or rollback operations.
> > What I receive is an error that says "..referral integrity violation
> > constraint xxx on table ..."
> > This xxx is exactly the primary-foreign-key connection mentioned above,
and
> > the 2 statements are both O.K (the values of primary-foreign-key
matches).
> > And furthermore I don't want to commit every statement (AutoCommit is
> > disabled).
> >
> > So, what do I have to do, that I can execute both statements and, if
O.K.,
> > then commit ............ ?
> >
> >
> > Thanks in advance.............GERD..................
> >
> >
> >
>
>
>
