New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Report more details for "object in use" errors [CORE4386] #4708
Comments
Modified by: @dyemanovassignee: Dmitry Yemanov [ dimitr ] |
Commented by: @dyemanov The simplest solution (e.g. "object INDEX "TEST_PK" is in use") is committed into v2.1 and v2.5, a more advanced solution is to be developed for v3. |
Modified by: @dyemanovFix Version: 3.0 Beta 2 [ 10586 ] |
Modified by: @pavel-zotovstatus: Resolved [ 5 ] => Resolved [ 5 ] QA Status: Deferred Test Details: Question in rus. forum: http://sql.ru/forum/1159875/vliyanie-commit-rollback-empty-line-pri-ddl-oshibkah-vnutri-execute-block-ah-na-stderr |
Modified by: @pavel-zotovstatus: Resolved [ 5 ] => Resolved [ 5 ] Test Details: Question in rus. forum: http://sql.ru/forum/1159875/vliyanie-commit-rollback-empty-line-pri-ddl-oshibkah-vnutri-execute-block-ah-na-stderr => Sent letter to dimitr, 19.06.2018 09:33 (checked on WI-V3.0.4.32988)
|
Modified by: @pavel-zotovstatus: Resolved [ 5 ] => Resolved [ 5 ] Test Details: Sent letter to dimitr, 19.06.2018 09:33 (checked on WI-V3.0.4.32988)
|
Modified by: @pavel-zotovstatus: Resolved [ 5 ] => Resolved [ 5 ] QA Status: Deferred => Done successfully Test Details: Empty name of procedure which is to be dropped but currently is used by another transaction, i.e.:- lock conflict on no wait transaction
|
Modified by: @pavel-zotovstatus: Resolved [ 5 ] => Closed [ 6 ] |
Submitted by: @dyemanov
Block progress on QA600
Votes: 3
While a proper metadata naming convention surely helps, the engine could be polite enough to report not only the name of the used object but its type (table/index/procedure/etc) as well. Also, for used indices currently a string "INDEX" is reported instead of the index name.
Thinking about this more, it would be great to have an original DDL command (or at least its shorthand) reported for any DFW error happening during commit. This would radically simplify debugging of multi-command DDL scripts.
Commits: fa22d85 6296318 a24fa92 FirebirdSQL/fbt-repository@4cbbdb1 FirebirdSQL/fbt-repository@9d08d40 FirebirdSQL/fbt-repository@b2cac4d
The text was updated successfully, but these errors were encountered: