Rather than outright deleting entities from the database, I would like to set a DeletedBy and DeletionDate in the database so that users will be able to, effectively, undelete information if they need to.

What would be the best way to accomplish this?

My current thought is to override the DeleteEntityCollection, DeleteEntity, and DeleteEntitiesDirectly methods to set the DeletedBy and DeletionDate fields and then call SaveEntity rather than DeleteEntity.

Is there a better/easier way to accomplish this within LLBLGen?

Thanks,

Jeremiah

I can't think of a better way within LLBLGen Pro. But I'd have made these into the BL if one exists. I mean I would modify my Delete methods which was calling the LLBLGen Pro Delete methods, to Update the entities with the needed info.

I've to seriously reconsider the use of soft-deletes (as these are called) and to not use them. The working set you'll work with is, over time, much smaller than the real # of rows in the db, which has issues on its own.

You should implement a delete trigger which copies the rows to an archive table, and an undelete should simply re-insert the entities. You can also circumvent this in the GUI, as deleting information is often not necessary, and IF people want to delete information, it is REALLY GONE. Why not simply leave the data there? And if you want to get rid of it, because it pollutes the workingset, ARCHIVE it. Because that's what you want: you want to delete the info, but in case some moron hits delete accidently and you want to get it back, it's not completely gone.

Repaving my windows partition also wipes everything clean, there's no undo option once I've formatted an fdisk-ed hdd.