You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It was mentioned here CORE2613 that starting from Firebird 2 it would be possible to create/drop foreign key while someone else is connected to a database, but I still have this issue with Firebird 2.1.3.
Error message:
ISC ERROR CODE:335544345
ISC ERROR MESSAGE:
lock conflict on no wait transaction
unsuccessful metadata update
object SCDESPV is in use
The text was updated successfully, but these errors were encountered:
This is support question and should be asked in support list
Creation of FK requires PR (protected read) locks on both relation's metadata.
I.e. if any if two relation is used by active concurrent transaction and this transaction hold PR or EX lock on relation's metadata, FK creation will fail.
Ask for more details in support list, if you really need it ;)
This link could be updated too http://www.firebirdfaq.org/faq22/. It also gives the impression that only earlier versions of Firebird had this limitation.
Can it be considered as a "Improvement" or "New Feature" then?
I face this problem since version 1.5, and disconnecting all users from database to maintain foreign keys is too stressful.
Submitted by: Felipe Jaekel (fkj)
Votes: 1
It was mentioned here CORE2613 that starting from Firebird 2 it would be possible to create/drop foreign key while someone else is connected to a database, but I still have this issue with Firebird 2.1.3.
Error message:
ISC ERROR CODE:335544345
ISC ERROR MESSAGE:
lock conflict on no wait transaction
unsuccessful metadata update
object SCDESPV is in use
The text was updated successfully, but these errors were encountered: