couchmonkey
08-18-2003, 10:49 AM
Maybe I should be looking for a db-focused board for this question, but I bet someone here has some good ideas.
I want to redesign a site so that volunteers can submit new content through a form: the content should be posted to a database but it won't be published until an editor (myself for now, but possibly multiple people in the future) has approved it. The question is, how do I set this up in my database?
One easy solution is simply to have an "approved" field in all of the necessary tables, and write all the queries so that they don't return records unless they're approved. Simple, but not very elegant because all of my PHP will have to be tailored for this approved field.
Another is to have a second database which holds unapproved content until it is approved, then records could just be copied from the "preproduction" database to the approved one. I like this solution, but more databases may equal more money. I could also do it by just duplicating all required tables and renaming them within the same database that the approved tables run on, but wouldn't that be bad database design?
Any comments or other solutions?
I want to redesign a site so that volunteers can submit new content through a form: the content should be posted to a database but it won't be published until an editor (myself for now, but possibly multiple people in the future) has approved it. The question is, how do I set this up in my database?
One easy solution is simply to have an "approved" field in all of the necessary tables, and write all the queries so that they don't return records unless they're approved. Simple, but not very elegant because all of my PHP will have to be tailored for this approved field.
Another is to have a second database which holds unapproved content until it is approved, then records could just be copied from the "preproduction" database to the approved one. I like this solution, but more databases may equal more money. I could also do it by just duplicating all required tables and renaming them within the same database that the approved tables run on, but wouldn't that be bad database design?
Any comments or other solutions?