db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel John Debrunner (JIRA)" <j...@apache.org>
Subject [jira] Assigned: (DERBY-1674) Investigate reducing the number of classes & methods in DataDictionary used to represent system tables
Date Sat, 03 Mar 2007 20:56:50 GMT

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

Daniel John Debrunner reassigned DERBY-1674:
--------------------------------------------

    Assignee:     (was: Daniel John Debrunner)

Only working on the sub-task DERBY-1734 at the moment.

> Investigate reducing the number of classes & methods  in DataDictionary used to represent
system tables
> -------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-1674
>                 URL: https://issues.apache.org/jira/browse/DERBY-1674
>             Project: Derby
>          Issue Type: Improvement
>          Components: SQL
>            Reporter: Daniel John Debrunner
>            Priority: Minor
>
> Currently two classes exists for each system table, one to represent the table (e.g.SYSTABLESRowFactory)
, one to represent a row (e.g. TableDescriptor)
> Look at having a single row factory (CatalogRowFactory) and using polymorphism (method
overloading) on the descriptor objects to perform the work
> that is done today (e.g. converting a descriptor to and from a Row object).
> In addition the DataDictionary has a specific method to drop each type of unique descriptor
(e.g. dropSPSDescriptor, dropAliasDescriptor)
> Would it be possible to have a single dropDescriptor(UniqueSQLObjectDescriptor) method
and again use polymorphism  on the descriptors.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message