|Subject||Odp: [firebird-support] Re: Insert ot update sta tements locks a table and all other instances th at try to run same statement are lcoked to|
Your assumption is wrong that logic is ok. You have problem with one installation probably because this client have havy load but others not.
Insert can only couse problem with unique constraint or reference to other tables or trigger on that record
Od: "doychin@... [firebird-support]" <firstname.lastname@example.org>
Temat: [firebird-support] Re: Insert ot update statements locks a table and all other instances that try to run same statement are lcoked to
Data: sob., wrz 6, 2014 21:12
Thank you for the idea but this is not what I'm looking for.
I think that inserting same record twice must produce error and not to to block the execution of other connections.
So in this case I'm trying to find where the problem is exactly.
This table is having problem with only one installation.
Another installation is having problem with another table.
I really don't think is a good idea to make changes to the logic that works perfectly on 20 other installations just because I have problem that is not in the logic with only one installation.
Is there any way to look in the firebird process where it is stuck?
I'll try to extract stack trace from java side.