On 5.06.2009 4:39, Karen Tracey wrote: > My first thought would be to not store that value in a model at all, but > rather pull it from the DB as max of the appropriate column when needed.
Yes, that would make things easier and more straightforward. But some features that are easy with my setup will then become more difficult: - leave out a series of numbers and create them later - start a journal with another number than 1 - create a document with a manually attributed number to fill a hole But thinking now about it, I have the feeling that you are right: I'll use the straightforward method ,and I will just have to use different ways to solve the exceptional cases. Thanks for your thoughts and greetings from Estonia! Luc --~--~---------~--~----~------------~-------~--~----~ 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 django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
