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

Statement completion of statement types that are DDL should drop the prepared statement [JDBC586] #617

Open
firebird-automations opened this issue Jun 16, 2019 · 1 comment

Comments

@firebird-automations
Copy link

Submitted by: @mrotteveel

Currently, Jaybird always prepares statements. For DDL statements it would be better if statement completion drops the prepared statement from the handle to avoid metadata locks being retained for too long.

@firebird-automations
Copy link
Author

Commented by: @mrotteveel

This ticket may be the result of an incorrect assumption, so investigate / reproduce the problem before implementing this. The actual observed problem may have been one of a delete statement retaining said lock.

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