2003-09-21 18:31:03 UTC
Hi, here I'am!
I can't check up the sql-tables completly. Description ends at 4th table ... some kind of graphical description (a use-case diagram too?) would be helpfull.
What I see is, that your intention is to imitate a *database in a database*, which is not such good idea - I carefully think. Building up the table-structure dynamicly by code and using the meta-data of the table where possible would be an propper alternative. *Structural data* which are hold as data in extra tables should be used as few as possible. This all makes the application slow and blown up.
A more detailed description of the usage of all this would be necessarily at first. You likly have already very distinct ideas of what to do whis that application: Should this become a programmable *interface* to databanks - or should there be GUI for *unknown* databank users.
If there shuold be a GUI we should think about that first: The biggest problem would be to provide the possibility of easy klicked solutions for complicated ER-relationships. To bring this structures into and out of databank would be the more easy part.
Last one: Is it realy needet to do so? There are already very simple web-frontends for databases (in progress). This is no accusation and no call up for resignation - this is the question for the special needs of this project.
Have a nice day!
