Issue Details (XML | Word | Printable)

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

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

For DSQL_unprepare and DSQL_drop, flush immediately

Created: 06/Mar/21 06:38 PM   Updated: 20/Mar/21 02:55 PM
Component/s: None
Affects Version/s: Jaybird 3.0.10, Jaybird 4.0.2
Fix Version/s: Jaybird 4.0.3, Jaybird 3.0.11, Jaybird 5

Issue Links:
Relate
 


 Description  « Hide
Currently, V11Statement#free(int) will not flush the free packet, deferring it for later processing when something else is sent over the connection. This behaviour is similar to fbclient.dll. The downside of this is that, when you close a prepared statement (or 'unprepare' a statement) and then do nothing else with the connection for a long time, the statement will retain existence locks on metadata objects.

Flushing immediately for DSQL_drop and DSQL_unprepare (and maybe not for DSQL_close) has the advantage that the prepared statement and its existence locks are released immediately and not deferred until some later activity on the connection.

 All   Comments   Change History   Subversion Commits      Sort Order: Ascending order - Click to sort in descending order

Mark Rotteveel added a comment - 20/Mar/21 07:35 AM