I have 30 years of experience with databases in my company. For 20 years we used the same field for multiple purporsespurposes when a new purporsepurpose was to be rarely used. It was okOK when we had HDD-sHDDs with 500Mb500MB. Over the time our databases became bigerbigger and bigerbigger, with hundreds of tables and fields. About 10 years ago we realized it is incresinglyincreasingly harder to maintanemaintain programs, and especialyespecially write updates of database structure besausebecause of this practice. Since then we add new fieldfields for new data. We still didhave not managed to update all multiple usages, and it has passedbeen 10 years. I strongly reccomend torecommend you add new fields for new data.
I have 30 years of experience with databases in my company. For 20 years we used same field for multiple purporses when new purporse was to be rarely used. It was ok when we had HDD-s with 500Mb. Over the time our databases became biger and biger with hundreds of tables and fields. About 10 years ago we realized it is incresingly harder to maintane programs and especialy write updates of database structure besause of this practice. Since then we add new field for new data. We still did not managed to update all multiple usages and it has passed 10 years. I strongly reccomend to add new fields for new data.
I have 30 years of experience with databases in my company. For 20 years we used the same field for multiple purposes when a new purpose was to be rarely used. It was OK when we had HDDs with 500MB. Over time our databases became bigger and bigger, with hundreds of tables and fields. About 10 years ago we realized it is increasingly harder to maintain programs, and especially write updates of database structure because of this practice. Since then we add new fields for new data. We still have not managed to update all multiple usages, and it has been 10 years. I strongly recommend you add new fields for new data.
I have 30 years of experience with databases in my company. For 20 years we used same field for multiple purporses when new purporse was to be rarely used. It was ok when we had HDD-s with 500Mb. Over the time our databases became biger and biger with hundreds of tables and fields. About 10 years ago we realized it is incresingly harder to maintane programs and especialy write updates of database structure besause of this practice. Since then we add new field for new data. We still did not managed to update all multiple usages and it has passed 10 years. I strongly reccomend to add new fields for new data.