I am *really* getting my butt kicked by this Data Model...
Originally Posted by Old Pedant
It may very well be that you have to abandon your idea of DIMENSIONS.
Nah, Debbie never accepts defeat!!
So, before I read your latest post I drew out another ERD which *logically* solves my problem. (The devil is in the physical implementation.)
I also looked at your latest proposal. It is a streamlined version, and I get it, but I think it falls victim to the same problem I keep running into.
If you look at all of our various "plans and schemes", there is a common theme...
The Data Models can be made to work "logically", but the challenge is, "How do you BUILD and SYNCHRONIZE the Junction Tables?!"
(If I'm wrong here, please correct me.)
For example, how would a person ENTER data - think in terms of a UI - to populate your latest Section_SubSection and Article_Placement junction tables??
And how would a person MAINTAIN data - think in terms of a UI - in both of those junction tables??
It's easy to manually populate the tables up front, but what happens when I change the relationship between Sections, SubSections and Articles? (Junction Tables need to be changed and synched as well...)
Admittedly, yours is much easier since there are only two Junction Tables which need to be kept in synch, but this is where I think I'm getting stuck.
(While I don't have the bandwidth for it, I might get stuck having to take a crash course in Triggers and Stored Procedures - assuming MySQL even has those?!)
What do you think about all of this?
Am I way off, or do I have a valid point?
And any suggestions on how to fix this?
It's a bummer, because I have an *awesome* new Logical ERD that I created last night, that could give me everything I want and need, but it also falls victim to the issue described above...
(Back to my evil scientist drawing board)