Yes, true, its a matter of trade offs. With a verison you add irrelavant data to your table schema. But potentially gain some performance. I tend to like my tables clean and relevant. Just a personal preference.
Plus it means the locking can work regardless of the table schema. Once you have to have a field in the schema you binding the functionality to the schema being right. A lot more chance of something going wrong. As for performance, I have done extensive tests for a BI system on large vs small Where clauses on Oracle, and counter-intuitivly the size of the where clause actually makes no measureable difference. I converted a 15 element where with likes, not ins, <>, etc.. clause into a two element where clause on over 4 million records. Measureable gain. Zero. Baffles the mind, but there you have it. I was just adding more ideas to the pot though :-) Use or ignore as you see fit. C --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~----------~----~----~----~------~----~------~--~---
