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

Ability to trace statements execution [JDBC597] #628

Closed
firebird-issue-importer opened this issue Oct 1, 2019 · 8 comments
Closed

Ability to trace statements execution [JDBC597] #628

firebird-issue-importer opened this issue Oct 1, 2019 · 8 comments

Comments

@firebird-issue-importer
Copy link

@firebird-issue-importer firebird-issue-importer commented Oct 1, 2019

Submitted by: @vasiliy-yashkov

Attachments:
jdp-2019-06-ability-to-control-statements-execution.md

Each statement has a StatementState, which allows to get the status of it, but specified mechanism does not allow to centrally monitor any statements synchronously. To do this need to wrap all statements at the application level and do this implementation there. However, at the application level, it is impossible to trace fetch, since it is impossible to subscribe to it. It is proposed to add a mechanism for synchronous tracing of all statements and fetches.

Commits: 2d1c37b 84fd175

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Oct 1, 2019

Commented by: @mrotteveel

I would like to have a Jaybird Design Proposal for this, see https://github.com/FirebirdSQL/jaybird/blob/master/devdoc/jdp/jdp-2019-01-jaybird-design-proposal.md

Specifically, I want a more detailed explanation of this feature, how this is expected to be used, and the reasons for this addition for Jaybird. And if possible, considered alternatives and implications of this change (eg security, possible misuse/memory leaks, etc).

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Oct 3, 2019

Commented by: @vasiliy-yashkov

This file provides a design proposal of the ability to control statements.

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Oct 3, 2019

Commented by: @mrotteveel

Thanks. As I also commented on the pull request, I'll provide feedback this weekend.

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Oct 12, 2019

Modified by: @mrotteveel

Fix Version: Jaybird 4.0.0-beta-2 [ 10902 ]

Fix Version: Jaybird 4 [ 10441 ]

description: Each statement has a StatementState, which allows to get the status of it, but specified mechanism does not allow to centrally monitor any statements synchronously. To do this need to wrap all statements at the application level and do this implementation there. However, at the application level, it is impossible to control fetch, since it is impossible to subscribe to it. It is proposed to add a mechanism for synchronous control all statements and fetches. => Each statement has a StatementState, which allows to get the status of it, but specified mechanism does not allow to centrally monitor any statements synchronously. To do this need to wrap all statements at the application level and do this implementation there. However, at the application level, it is impossible to trace fetch, since it is impossible to subscribe to it. It is proposed to add a mechanism for synchronous tracing of all statements and fetches.

summary: Ability to control statements execution => Ability to trace statements execution

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Oct 12, 2019

Commented by: @mrotteveel

I have merged this with some changes, see 52a0fbb

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Oct 12, 2019

Modified by: @mrotteveel

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

resolution: Fixed [ 1 ]

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Jan 19, 2020

Modified by: @mrotteveel

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

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

Successfully merging a pull request may close this issue.

None yet
2 participants