[thelist] MySQL database optimis(z)ation
rudy
r937 at interlog.com
Mon Feb 4 08:51:01 CST 2002
> I know that some versions of MySQL are not able to do subselects,
> but what is the major downside of the following strategy (which is a
> *fairly* normalized structure):
holy non sequitur, batman
> It's a very complex system, which is one downside,
> but it very extensible.
yeah, it looks extensible -- any time a design has "type" tables, there's
usually planned extensibility
> Can you help us identify some of the other issues involved
> with such a structure?
i don't mean to make light of this, but the only issue i can see at the
moment is understandability, because from the table layouts you've
provided, it's hard to see how it works (i *think* i finally got it)
when presenting data designs, sample data is often helpful
especially if you have columns named id, story_type_id, id (PK), id (PK),
story_type_id (FK to story_type table), story_id (FK to story table, part
of PK), and data_type_id (FK to story_type_data_type, other part of PK)
... if you know what i mean ;o)
rudy
More information about the thelist
mailing list