Hi! On Wed, Aug 11, 2010 at 12:47 PM, Piper, Adam <[email protected]> wrote: > There are a number of possible solutions we have discussed, with the > example being wiki pages: > > 1. Versions < 1 > > Alter the DELETE to be an UPDATE which decrements the version to the > next available number below 1. Alter the SELECT to take only items with > versions above 0.
Wouldn't it be easier just to negate ID, not to search for next available number? Delete can be then just one simple UPDATE statement. This means that information about deletion status would be stored in highest ID bit. What suggest that this could be normalized in another field. > 2. "deleted" column, version skipping Yes. So this is then just a question: should be normalize or should we not. For me ID mingling is ugly. It is not conceptually clean concept. Mitar -- You received this message because you are subscribed to the Google Groups "Trac Development" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/trac-dev?hl=en.
