Having such a isDelete flag also allows to make funny perfmance tuning stuff on db side.
I'm thinking, for instance, about splitting the table in two data files. First one contains the rows marked as deleted, known to be readonly, and to always grow, could be placed on the slowest storage device, second file for the active part of table, place on the fastest device...
Having such a flag also allows to make funny perfmance tuning stuff on db side. I'm thinking, for instance, about splitting the table in two data files. First one contains the rows marked as deleted, known to be readonly, and to always grow, could be placed on the slowest storage device, second file for the part of table, place on the fastest device...