php record backup idea -- need second opinion please.
Posted: Sat Aug 29, 2009 10:27 am
Hello,
Recently I launched an application to build inter-departmental newsletters and have been fine tuning since. But I am starting as it is being used more and more, I am wondering about when things are 'accidentally deleted'...I don't have a lot of experience in this area (only have built 'toy' programs that aren't used for anything).
So I have a couple of ideas of how to go about this, but this is what I am hoping to do. I would like to Copy or move the data that is being deleted to another location. This location could be a file, or another table in the database. But ideally I am hoping to provide a way that the users can resurrect accidentally removed items.
I have thought about this for a while now, and I am running into a snag here (due to lack of experience). The person in charge of the newsletters wants a way to remove newsletters (say one is accidentally created for the wrong day), and removing the entire newsletter is the problem.
My tables are organized like so:
Ideally, when the newsletter is deleted, it could copy numerous sections and numerous articles.
I feel I am getting a case of 'tunnel vision' here, and could use another apporach or insight.
Thanks in advance
Daniel
PS. if it seems like I am being over protective for the users sake, the people that use this system, I am supprised they can turn their own computers on.
Recently I launched an application to build inter-departmental newsletters and have been fine tuning since. But I am starting as it is being used more and more, I am wondering about when things are 'accidentally deleted'...I don't have a lot of experience in this area (only have built 'toy' programs that aren't used for anything).
So I have a couple of ideas of how to go about this, but this is what I am hoping to do. I would like to Copy or move the data that is being deleted to another location. This location could be a file, or another table in the database. But ideally I am hoping to provide a way that the users can resurrect accidentally removed items.
I have thought about this for a while now, and I am running into a snag here (due to lack of experience). The person in charge of the newsletters wants a way to remove newsletters (say one is accidentally created for the wrong day), and removing the entire newsletter is the problem.
My tables are organized like so:
Code: Select all
newsLetter newsLetterSections articles
----------- -------------------- ------------
newsLetterID newsLetterID articleID
newsLetterTitle sectionID sectionID
sectionTitle articleTitle
articleBody
articleURL
Ideally, when the newsletter is deleted, it could copy numerous sections and numerous articles.
I feel I am getting a case of 'tunnel vision' here, and could use another apporach or insight.
Thanks in advance
Daniel
PS. if it seems like I am being over protective for the users sake, the people that use this system, I am supprised they can turn their own computers on.