Issue Details (XML | Word | Printable)

Key: JDBC-597
Type: Improvement Improvement
Status: Closed Closed
Resolution: Fixed
Priority: Major Major
Assignee: Mark Rotteveel
Reporter: Vasiliy Yashkov
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
Jaybird JDBC Driver

Ability to trace statements execution

Created: 01/Oct/19 12:42 PM   Updated: 19/Jan/20 04:59 PM
Component/s: JDBC driver
Affects Version/s: Jaybird 3.0.7, Jaybird 4.0.0-beta-2
Fix Version/s: Jaybird 4.0.0-beta-2, Jaybird 4

File Attachments: 1. File jdp-2019-06-ability-to-control-statements-execution.md (4 kB)



 Description  « Hide
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.

 All   Comments   Change History   Subversion Commits      Sort Order: Descending order - Click to sort in ascending order
Mark Rotteveel added a comment - 12/Oct/19 03:51 PM

Mark Rotteveel added a comment - 03/Oct/19 04:33 PM
Thanks. As I also commented on the pull request, I'll provide feedback this weekend.

Vasiliy Yashkov added a comment - 03/Oct/19 12:36 PM
This file provides a design proposal of the ability to control statements.

Mark Rotteveel added a comment - 01/Oct/19 06:00 PM
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).