Re: Best practices for deleting and restoring records - moving vs flagging

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Saqib Ali wrote:
Hello All,

What are best practices for deleting records in a DB. We need the
ability to restore the records.

Two obvious choices are:

1) Flag them deleted or undeleted
2) Move the deleted records to seperate table for deleted records.

We have a  complex schema. However the the records that need to be
deleted and restored reside in 2 different tables (Table1 and Table2).

Table2 uses the primary key of the Table1 as the Foriegn key. The
Primary key for Table1 is auto-generated. This make the restoring with
the same primary key impossible, if we move deleted data to a

why is restoring auto-generated keys impossible? do you have that many records
that the auto-gen rolls over? also if it is auto-generated then technically
I don't see a reason that generating a new id upon re-insertion would
be problematic - the id is just an arbitrary unique identifier - as long
as you keep the link between reinserted records in table1 en table2
(given the id maybe used else where!).

sounds like flagging it easier regardless of what is better performance-wise.

different table. However if we just flag the record as deleted the
restoring is quite easy.

Any thoughts/ideas ?


--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php


[Index of Archives]     [PHP Home]     [Apache Users]     [PHP on Windows]     [Kernel Newbies]     [PHP Install]     [PHP Classes]     [Pear]     [Postgresql]     [Postgresql PHP]     [PHP on Windows]     [PHP Database Programming]     [PHP SOAP]

  Powered by Linux