[DERBY-1674] Investigate reducing the number of classes & methods in DataDictionary used to represent system tables

• Type: Improvement
• Status: Open
• Priority: Minor
• Resolution: Unresolved
• Component/s: SQL
• Labels: derby_triage10_11
• Urgency: Low
• Assignee: Unassigned
• Reporter: Daniel John Debrunner
• Created: 11/Aug/06 17:51
• Updated: 25/Jun/13 14:37

Description

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.

Issue Links

• relates to: DERBY-1664 Derby startup time is too slow

Sub-Tasks

• Simplify building of SystemColumn array in CatalogRowFactory implementations.: Closed
• Index column names in CatalogRowFactory implementations are not required: Closed