Simply SQL CMS App - why is content stored in another table
Hi Rudy, I'm loving your book!
I do have one question though, in the CMS app you have in there, you've defined a seperate 'content' table for the entries' content - why did you do this?
if it's just a 1-to-1 relationship why not just store it in the entries table?
I do understand that some entries might have different sorts of content which may be stored in different tables but even so wouldn't that require a different table structure anyway?