Unanswered: Database Design Pattern for blog-type article storage
How would be the best way to store an article that could contain images or other objects? A user would enter their article using an FCKEditor and can embed a number of objects. Submission would store their article (same concept as a blog).
However, analysis shows I cannot simply upload the object and store on the server because if the article is edited or deleted, the link to the object will be remove (in the case of a delete), yet the object will remain.
And I cannot store the objects in a separate table with a FK to the article, and a numeral pointing to the position in the article (makes editing a mess, think md5-messy).