> Fuse Table (this table brings the pages and sections together)
> --
> fuseID, sectionID, pageID
I'd get rid of the fuseID and just use sectionID and pageID as a
combined primary key -- you're never going to have more than one copy of
a given page in a given section so you can
I did a thing I called 'mirroring' wherein the user decides individually whether or
not a page somewhere else should be shown in the current location. The page record
has a 'mirror' field that, if an ID is in there, then that ID is used for data
retrieval rather than the 'true' current page. M
Create
PageTable
--
pageID, content
Fuse Table (this table brings the pages and sections together)
--
fuseID, sectionID, pageID
Section Table
--
sectionID, sectionName
Then, you can call ALL pages that have sectionID = XX Thus, a page
3 matches
Mail list logo
