joel24 Posted January 2, 2011 Share Posted January 2, 2011 Just wondering whether to set a 'deleted' column to either 1 or 0 (true/false) or allow users to delete the row... some other tables rely on rows in other tables as foreign keys, so deleting them would disrupt this though how would keeping the rows impact on performance...? throw me your ideas! Quote Link to comment Share on other sites More sharing options...
BLaZuRE Posted January 2, 2011 Share Posted January 2, 2011 I never allow users to delete rows. They may delete something they shouldn't and whine later. Yes, I would set a column to deleted with tinyint. I don't see it as a big performance hit. If you have hundreds or thousands of rows, consider exporting them to another table or database or deleting them if it's reasonable every X days/weeks/months. It such a scenario, I'm worried more about code performance than database performance. i.e., if you connect multiple times to gather the same data. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.