Title: Re: [Firebird-devel] ODP: ODP: ODP: Inserts and FKs
If you had understood the case, you would have noticed that the transaction in isql-1 doesn't matter. Either readcommited or snapshot will show the same result. That's why I didn't mind about running set transaction in
Why do you think that one isql have transaction read commited but second have
snapshot? I do not see your transaction command. If you depend on automatic
transactions started by isql, then both are the same, no
randomness...Regards,Karol Bieniaszewski
nullFirebird-Devel mailing list, web interfa
Let's go, based on Karol's previous example.
Open two isql sessions (isql1 and isql2) connected to the same database, and
follow the sequence of commands in this order:
isql1:
CREATE TABLE A
(
ID BIGINT NOT null PRIMARY KEY);
CREATE TABLE B
(
ID BIGINT NOT null PRIMARY KEY,
ID_A BIGINT NOT NUL
06.09.2019 23:00, Carlos H. Cantu wrote:
Sending screenshots of the isql sessions will not help, since what really matters is the
time of starting/commit the transactions.
You don't need to send screenshots. Send script. Second instance of isql can be run in
the right moment using command "s
Title: Re: ODP: [Firebird-devel] ODP: ODP: Inserts and FKs
You can use your own example (that you sent before), just follow the comments that I marked in red, and you will reproduce the problem.
Sending screenshots of the isql sessions will not help, since what really matters is the time of st
Better show your commands in isql then we can reproduce problem.
Regards,
Karol Bieniaszewski
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
