You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Myrna van Lunteren (JIRA)" <ji...@apache.org> on 2009/03/18 04:52:50 UTC
[jira] Created: (DERBY-4101) Further improvements to schema
does not exist fix - DERBY-3043
Further improvements to schema <scgenabane> does not exist fix - DERBY-3043
---------------------------------------------------------------------------
Key: DERBY-4101
URL: https://issues.apache.org/jira/browse/DERBY-4101
Project: Derby
Issue Type: Bug
Affects Versions: 10.5.0.0
Reporter: Myrna van Lunteren
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.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DERBY-4101) Further improvements to schema
does not exist fix - DERBY-3043
Posted by "Myrna van Lunteren (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-4101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Myrna van Lunteren updated DERBY-4101:
--------------------------------------
Issue Type: Improvement (was: Bug)
> 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
> Affects Versions: 10.5.0.0
> Reporter: Myrna van Lunteren
>
> 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.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DERBY-4101) Further improvements to schema
does not exist fix - DERBY-3043
Posted by "Myrna van Lunteren (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-4101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Myrna van Lunteren updated DERBY-4101:
--------------------------------------
Comment: was deleted
(was: bad ten-finger blind typing.)
> 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: Bug
> Affects Versions: 10.5.0.0
> Reporter: Myrna van Lunteren
>
> 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.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DERBY-4101) Further improvements to schema
does not exist fix - DERBY-3043
Posted by "Myrna van Lunteren (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-4101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Myrna van Lunteren updated DERBY-4101:
--------------------------------------
Summary: Further improvements to schema <schemaname> does not exist fix - DERBY-3043 (was: Further improvements to schema <scgenabane> does not exist fix - DERBY-3043)
bad ten-finger blind typing.
> 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: Bug
> Affects Versions: 10.5.0.0
> Reporter: Myrna van Lunteren
>
> 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.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DERBY-4101) Further improvements to schema
does not exist fix - DERBY-3043
Posted by "Mike Matrigali (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-4101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mike Matrigali updated DERBY-4101:
----------------------------------
Component/s: SQL
> 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: 10.5.1.1
> Reporter: Myrna van Lunteren
>
> 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.
-
You can reply to this email to add a comment to the issue online.