> Django is optimized for the common case. Sure, it may well be that > it's easy to accommodate uncommon cases as well, and when it's > reasonable, we should definitely do so, but the reason it hasn't been > up to this point is simply that not enough people need it.
I agree fully. I've only needed to do this a couple of times. > Call me crazy, but why would an AutoField help you with that? Since > you later explain that the records are created in satellite systems, > then aggregated, wouldn't you still run into problems ordering by > something that's generated in isolation? It sounds like what you > really want is a DateTimeField(default=datetime.datetime.now). That > way, you get orderable fields that can be combined from any number of > sources without worrying about collisions. Plus, you get the added > bonus of having a real-world value that you can use for more than just > ordering. I was hoping to spare us the gory detail. Crazy Gul, ;-) the order of the records, in my case, is only important in the context of a foreign in key. The records in this table are grouped based on records in another table. I only need the correct order for the group, not the entire table or aggregated tables. Since entire groups are created on single satellite servers, never spanning servers, the group order is maintained when the records are aggregated. Using a datatime will not work if you are adding a thousand records per second or if somebody or some thing "adjusts" your system clock. It can happen... Cheers, Andy --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" 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/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
