On Thu, 19 Jun 2003, Matthew Nuzum wrote:
> Regarding backup history:
>
> I have an application designed for novices. Apparently it's easy to hit the
> "Delete" button, and then say yes to the "Are you sure you want to delete
> this?" question even when they don't want to. Therefore I simply mar
Regarding backup history:
I have an application designed for novices. Apparently it's easy to hit the
"Delete" button, and then say yes to the "Are you sure you want to delete
this?" question even when they don't want to. Therefore I simply mark a
record as deleted. For example,
UPDATE table SE
On your second question:
Keeping old data helps with data analysis, i.e., data mining. I would do the fired date as transactions. To see if an employee is still and employee, look for the latest transation, hired, rehired, contracted with as a temp/consultant, fired, laid off, etc.
Antonios Chris
Antonios Christofides <[EMAIL PROTECTED]> writes:
> Is this filenames-instead-of-BLOBs for easier backup common practice?
> Any other ideas or comments?
This is a major point of contention. Some people think keeping all data in the
database is a better approach, others think data that isn't inhe
