dcsimg
Design for maintaining lookup tables
2 posts in topic
Flat View  Flat View
TOPIC ACTIONS:
 

Posted By:   Anonymous
Posted On:   Monday, March 3, 2003 08:53 AM

Hi all,
I am developing an application to maintain lookup tables. Since the number of tables can grow in the furture, I am planning to a generic design.

Any suggestion or ideas?

Re: Design for maintaining lookup tables

Posted By:   Anonymous  
Posted On:   Tuesday, March 4, 2003 12:45 AM

Yes - don't make the current design more generic than you need it *now*. Invest the saved time in an extensive test-suite.

Once you *need* a more generic design, refactor it to be more generic. This way you design to actual requirements, not to some speculations - and the tests will make sure that you don't break anything by changing the design.

Sounds reasonable?

Re: Design for maintaining lookup tables

Posted By:   Pankaj_Soni  
Posted On:   Monday, March 3, 2003 09:15 AM

Instead of going for multiple tables try creating a single table "lookup" and have fields like section, subsection...(the depth can be determined by number of levels you want to have) and then having key value pairs.

This would make your desin and code very generic where you have one table and perhaps one java class where you pass the requisite parameters.
About | Sitemap | Contact