normal form!

[ian_evil]

Just double checking, but when a database is properly normalized and being used in a content management site, things like forums and user blogs will each get their own tables, right? So when user #00456 activates an account, (and has their user info added to the "site_users" table) a table named "site_users_blog_00456" with a (for example) 'user_id

Comments

[mkb_technologie]

a proper relational database will definitely have a lot of tables. It's not for scalability purposes but more to make sure you don't have the same datum in multiple places. this removes the possibility of a conflict in your data. it's for integrity.

[mkb_technologie]

yeah, that was a pre-coffee reply :(

[lorele]

Yeah... Sucks.

[mkb_technologie]

OH FUCK i missed that line.

[ian_evil]

Yeah. While I'm not 100% sure I get what you're describing as the proper design (I'll read it a few more times after I get some sleep), I figured out right after I posted that how little sense it made. I'm trying to figure out short cuts. Which is probably the wrong way to start.

But hey, when I finish my flowchart you guys can all proof it.