db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Knut Anders Hatlen (JIRA)" <derby-...@db.apache.org>
Subject [jira] Updated: (DERBY-1176) Stored prepared statements in the SYSIBM schema are not updated on upgrade
Date Fri, 07 Apr 2006 08:37:37 GMT
     [ http://issues.apache.org/jira/browse/DERBY-1176?page=all ]

Knut Anders Hatlen updated DERBY-1176:

    Attachment: derby-1176-v1.diff

'derby-1176-v1.diff' makes the metadata calls that depend on
SYSIBM.METADATA return the correct results after an upgrade from 10.1
(soft or hard).

  1. DD_Version.doFullUpgrade() now drops and recreates SPSs in all
     system schemas, not SYSIBM only.

  2. EmbedDatabaseMetaData already has the necessary machinery to load
     queries from system tables or metadata.properties depending on
     whether the engine is in soft upgrade mode or not. I extended it
     so that it could read queries from metadata_net.properties as

  3. New method EmbedDatabaseMetaData.getClientCachedMetaData() which
     executes SYSIBM.METADATA (either from system table or
     metadata_net.properties) to fetch the metadata that will be
     cached on the client.

  4. SystemProcedures.METADATA() now invokes
     EmbedDatabaseMetaData.getClientCachedMetaData() instead of
     executing the METADATA SPS directly.

The patch passes derbyall and the upgrade test. I have verified
manually that the metadata calls on the client return the correct
values in soft and hard upgrade.

Please review. Thanks.

> Stored prepared statements in the SYSIBM schema are not updated on upgrade
> --------------------------------------------------------------------------
>          Key: DERBY-1176
>          URL: http://issues.apache.org/jira/browse/DERBY-1176
>      Project: Derby
>         Type: Bug

>   Components: JDBC
>     Versions:
>     Reporter: Knut Anders Hatlen
>     Assignee: Knut Anders Hatlen
>  Attachments: derby-1176-v1.diff, derby-1176-v1.stat
> When upgrading a database created with Derby 10.1 to 10.2, the SPSs in
> the SYSIBM schema are not updated. SYSIBM.METADATA was modified in
> DERBY-965, but it still has the old behaviour after the upgrade (both soft and
> hard).
> How to reproduce:
>   1. Create a database with 10.1.
>     soft upgrade:
>   2. Start 10.2 network server.
>   3. Connect to the 10.1 database with the 10.2 client driver and
>      invoke DatabaseMetaData.supportsResultSetConcurrency(
>      ResultSet.TYPE_FORWARD_ONLY, ResultSet.CONCUR_READ_ONLY). Return
>      value: FALSE.
>     hard upgrade:
>   4. Restart 10.2 network server.
>   5. Connect to the database with "upgrade=true" added to the
>      URL. DatabaseMetaData.supportsResultSetConcurrency(
>      Restart.TYPE_FORWARD_ONLY, ResultSet.CONCUR_READ_ONLY) returns
>      FALSE.
>     observe correct behaviour:
>   6. Delete the database and recreate it with 10.2.
>   7. Start 10.2 network server.
>   8. Connect to the database with the client driver and invoke
>      DatabaseMetaData.supportsResultSetConcurrency(
>      Restart.TYPE_FORWARD_ONLY, ResultSet.CONCUR_READ_ONLY). Return
>      value: TRUE.
> Proposed solution for hard upgrade: drop and recreate SPSs.
> Proposed solution for soft upgrade: read SYSIBM.METADATA from
> metadata_net.properties.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message