Hi, guys...
just want to share some programming thoughts with you..umm some geeky ones...isn't that the lebgeeks forum :P.. it is fine if u did not get this, found it stupid :P

there is a type of users that DBAs and Programmers call Pain in the A**
that is the press-delete button user, and i want my data back (nag..shout..cry..more wining...and more na2 w headache)

so i was thinking that maybe after all we should not actually delete the data in some table, y not put a status flag
my relational database table would be like :
code(numeric) name(nvarchar[50]) stat (bit)

of course u guessed it, i will use the 1 and 0 to signal if the record is visible yes or no...but of course that will work only with small record counting tables like the employees or holidays :P :P table and it is somehow a hastle in programing as every select must have an additional condition

for the big and critical tables like money_transaction that won't really work another solution is to do a history_tblname table and move the records instead of deleting
that will increase the number of lines in ur code and u will do 2 transactions instead of one :( , but still somehow acceptable i think
this got me thinking if i can add special SQL like MIRDEL from tb1 to tb2 where condition :P , this will do those 2 transactions in 1 ,is there anything similar to the MIRDEL that can do that...anyone knows ?

I know that some of you might be thinking, but hey do a daily backup and u are done... well that can be easily done of course, but in some cases it won't work as some user can really f*** up a database in less than a min, and backup becomes not that useful and of course u hear the complain about re-doing the work, and in some systems there are transactions in one table that u need to Virtually delete and backup the whole complete database is a waste of storage and takes time, and have u ever heard about the wacked weird wanted reports that must contain data previous,current and future data (yes i did report that would predict accounting numbers after 2 years according to the current rythm :( [...was a pain]

So what u think of my Virtual Delete?
anyone had this idea before ? how do u as a programmer judge it?
do u think this can be done in real life systems ? would u dare to do it :P as programmer ? anyone knows any sql command that moves a special record from a table without using insert/delete
w heik, just share ur delete thoughts ....

HEHEHE.. oops that was long weird post ..