db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mamta A. Satoor (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (DERBY-4101) Further improvements to schema <schemaname> does not exist fix - DERBY-3043
Date Sun, 30 Sep 2012 01:38:07 GMT

     [ https://issues.apache.org/jira/browse/DERBY-4101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Mamta A. Satoor updated DERBY-4101:

    Urgency: Normal
     Labels: derby_triage10_10  (was: )
> Further improvements to schema <schemaname> does not exist fix - DERBY-3043
> ---------------------------------------------------------------------------
>                 Key: DERBY-4101
>                 URL: https://issues.apache.org/jira/browse/DERBY-4101
>             Project: Derby
>          Issue Type: Improvement
>          Components: SQL
>    Affects Versions:
>            Reporter: Myrna van Lunteren
>              Labels: derby_triage10_10
> DERBY-3043 was fixed, but a number of comments were raised, specifically because of meshing
code from the fix of DERBY-3266, that warrant follow-up:
> instead of current code, make another overload of getSchemaDescriptor(<int:tabletype>)
and use that
> consistently in CreateTableNode and DropTableNode.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message