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

Use of named cursor fails if statement was not executed [CORE4505] #4824

Closed
firebird-automations opened this issue Jul 31, 2014 · 7 comments
Closed

Comments

@firebird-automations
Copy link
Collaborator

Submitted by: @AlexPeshkoff

Is related to CORE4489

Originally noticed by Adriano:

setCursorName was moved into IResultSet.
IMO makes no sense to first open the cursor and then name it later.
We can have two prepared statement, while the second uses the cursor
name of the first. But now we need to open the first before prepare the
second.

Commits: 900fb82 FirebirdSQL/fbt-repository@046ce12

@firebird-automations
Copy link
Collaborator Author

Modified by: @AlexPeshkoff

assignee: Alexander Peshkov [ alexpeshkoff ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @AlexPeshkoff

Link: This issue is related to CORE4489 [ CORE4489 ]

@firebird-automations
Copy link
Collaborator Author

Commented by: @AlexPeshkoff

1. setCursorName() moved back to IStatement.
2. Added parameter cursorName to IAttachment::openCursor().
3. Enabled changing currsor name for prepared statements in new OO API.
4. Restored functionality of ISC API.

@firebird-automations
Copy link
Collaborator Author

Modified by: @AlexPeshkoff

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

resolution: Fixed [ 1 ]

Fix Version: 3.0 Beta 1 [ 10332 ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @AlexPeshkoff

description: Originally noticed by Adriano:

setCursorName was moved into IRFesultSet.
IMO makes no sense to first open the cursor and then name it later.
We can have two prepared statement, while the second uses the cursor
name of the first. But now we need to open the first before prepare the
second.

=>

Originally noticed by Adriano:

setCursorName was moved into IResultSet.
IMO makes no sense to first open the cursor and then name it later.
We can have two prepared statement, while the second uses the cursor
name of the first. But now we need to open the first before prepare the
second.

@firebird-automations
Copy link
Collaborator Author

Modified by: @pcisar

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

@firebird-automations
Copy link
Collaborator Author

Modified by: @pavel-zotov

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

QA Status: No test

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

No branches or pull requests

2 participants