Subject:
|
Re: A Technic set DB outline
|
Newsgroups:
|
lugnet.admin.database
|
Date:
|
Tue, 1 Dec 1998 20:07:27 GMT
|
Viewed:
|
835 times
|
| |
|
|
Larry Pieniazek wrote:
>
> First off, let me state that were I designing this from scratch I'd do
> an object model not a data model but...
> Jim Hughes wrote:
> > >
> > > Theme table seems empty.
> >
> > It is. I am still trying to figure out how to put themes and subthemes
> > into a table.
>
> You need a hierarchy table. Model it like this (not legit SQL)
>
> Table Theme
> ThemeID integer PRIMARY KEY NOT NIL
> ThemeType Code /* maps to code table with values such as "system",
> "theme", "subtheme" etc... */ NOT NIL
> Name Varchar80
> Description Varchar255
> ParentTheme (->ThemeID) integer
>
> Now you have one theme that has a nil ParentTheme and type code of
> "root"
> Each SYSTEM theme the has root as parent
> Each theme like town has a SYSTEM theme as parent
> Each subtheme like Race has a theme as parent, and so forth.
In case accuracy WRT TLG is important here, the actual hierarchy looks
like the following (I may never forgive Todd for his invention of the
term "subtheme" :-P)
Product Programme
+- Product Line
+- Product Theme
"Race" is a theme in the "Town System" Product Line which is part of
the "LEGO System" Product Programme (other PP's are DUPLO and
TECHNIC). Product lines and themes can be variously referred to as
"line" (no product in front) or "series".
The hierarchy comes from TLG documentation that was put out late-80s
early-90s, which very specifically spelled out the entire product
offering at that time. Lately, there has been further and further
blurring of the idea of Product Line versus Theme, so this may no
longer apply, but please note that "subtheme" has never been, strickly
speaking, correct.
-- joshua
|
|
Message has 1 Reply:
 | | Re: A Technic set DB outline
|
| (...) Eh, whenever did I invent that term? And what have I done to popularize it? The weird term I made up for the FLG was "series." I don't like subtheme either, unless there is also the concept of supertheme -- as in subcategory and supercategory. (...) (26 years ago, 1-Dec-98, to lugnet.admin.database)
|
Message is in Reply To:
| | Re: A Technic set DB outline
|
| First off, let me state that were I designing this from scratch I'd do an object model not a data model but... (...) You need a hierarchy table. Model it like this (not legit SQL) Table Theme ThemeID integer PRIMARY KEY NOT NIL ThemeType Code /* (...) (26 years ago, 30-Nov-98, to lugnet.admin.database)
|
9 Messages in This Thread:
 
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
This Message and its Replies on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
Active threads in Database
|
|
|
|
|
|
