[
https://issues.apache.org/jira/browse/DERBY-3723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kristian Waagan updated DERBY-3723:
-----------------------------------
Derby Info: [Patch Available]
> Reset current schema to default (user name) when creating a new logical
> connection in the client driver
> -------------------------------------------------------------------------------------------------------
>
> Key: DERBY-3723
> URL: https://issues.apache.org/jira/browse/DERBY-3723
> Project: Derby
> Issue Type: Improvement
> Components: JDBC, Network Client
> Affects Versions: 10.1.3.1, 10.2.2.0, 10.3.3.0, 10.4.1.3
> Environment: Primarily when connection pooling and statement caching
> are used.
> Reporter: Kristian Waagan
> Assignee: Kristian Waagan
> Priority: Minor
> Fix For: 10.4.1.4, 10.5.0.0
>
> Attachments: derby-3723-1a-client_schema_reset.diff
>
>
> The current schema is used as part of the lookup key for the client side JDBC
> statement cache. With the current implementation, the schema is explicitly
> fetched from the server by executing a "VALUES CURRENT SCHEMA" query after a
> new logical connection has been created. This hurts performance when using
> the JDBC statement cache, and in some cases it performs worse than running
> without a client side JDBC statement cache.
> The performance can be improved by resetting the current schema to the
> default on the client when a new logical connection is created. The user name
> is used as the default schema in Derby.
> Note that this issue is regarding logical connections. There is no API for
> changing the user name, or default schema, for a logical connection. This
> ensures the schema must be set to the associated user name for a newly
> created logical connection.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
