Skip to content
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

Error "no current record for fetch operation" is raised while deleting record from MON$ATTACHMENTS using ORDER BY clause [CORE5684] #5950

Closed
firebird-issue-importer opened this issue Dec 18, 2017 · 9 comments

Comments

@firebird-issue-importer

Submitted by: @pavel-zotov

Connect to any database and type:

SQL> commit; delete from mon$attachments order by mon$attachment_id rows 1;

Output will be:

Statement failed, SQLSTATE = 22000
no current record for fetch operation

Checked on 2.5.8, 3.0.3, 4.0 Alpha 1

PS. I reduced priority to "minor" as this looks like 'strange warning' rather than real bug.

Commits: 9555ff0 c67c6a0 1c2d427

@firebird-issue-importer
Copy link
Author

firebird-issue-importer commented Dec 18, 2017

Modified by: @pavel-zotov

priority: Major [ 3 ] => Minor [ 4 ]

Component: Engine [ 10000 ]

description: Connect to any database and type:

SQL> commit; delete from mon$attachments order by mon$attachment_id rows 1;

Output will be:

Statement failed, SQLSTATE = 22000
no current record for fetch operation

Checked on 2.5.8, 3.0.3, 4.0 Alpha 1

=>

Connect to any database and type:

SQL> commit; delete from mon$attachments order by mon$attachment_id rows 1;

Output will be:

Statement failed, SQLSTATE = 22000
no current record for fetch operation

Checked on 2.5.8, 3.0.3, 4.0 Alpha 1

PS. I reduced priority to "minor" as this looks like 'strange warning' rather than real bug.

@firebird-issue-importer
Copy link
Author

firebird-issue-importer commented Dec 18, 2017

Commented by: Sean Leyne (seanleyne)

Executing such a statement results in the current attachment/connection being deleted/broken, IMO the use case is completely illogical.

@firebird-issue-importer
Copy link
Author

firebird-issue-importer commented Dec 19, 2017

Commented by: @dyemanov

Sean, test case is just to reproduce the problem, it can be dumb ;-) This error has nothing to do with what attachment is being forcibly shutdown.

@firebird-issue-importer
Copy link
Author

firebird-issue-importer commented Dec 19, 2017

Modified by: @dyemanov

assignee: Dmitry Yemanov [ dimitr ]

@firebird-issue-importer
Copy link
Author

firebird-issue-importer commented Dec 19, 2017

Modified by: @dyemanov

summary: Exception "no current record for fetch operation" appears after delete attach in mon$attachments with specifying 'order by' clause => Error "no current record for fetch operation" is raised while deleting record from MON$ATTACHMENTS using ORDER BY clause

@firebird-issue-importer
Copy link
Author

firebird-issue-importer commented Dec 19, 2017

Modified by: @dyemanov

Fix Version: 2.5.8 [ 10809 ]

@firebird-issue-importer
Copy link
Author

firebird-issue-importer commented Dec 20, 2017

Modified by: @dyemanov

status: Open [ 1 ] => Resolved [ 5 ]

resolution: Fixed [ 1 ]

Fix Version: 3.0.3 [ 10810 ]

Fix Version: 4.0 Beta 1 [ 10750 ]

@firebird-issue-importer
Copy link
Author

firebird-issue-importer commented Dec 21, 2017

Modified by: @pavel-zotov

status: Resolved [ 5 ] => Resolved [ 5 ]

QA Status: No test => Done successfully

@firebird-issue-importer
Copy link
Author

firebird-issue-importer commented Dec 21, 2017

Modified by: @pavel-zotov

status: Resolved [ 5 ] => Closed [ 6 ]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment