pbx wrote:
>I've been banging my head against some similar problems recently,
>mostly with legacy data that's poorly normalized. One optimization/hack
>that was suggested to me was adding a field that's only used for
>sorting (or selecting, as the case may be) -- like your hypothetical
>concatenated string -- and generating it at creation/update time with a
>pre-save hook.
>
>
On pre-save of what? When you do
entry.authors.add(Author(...))
... entry's save() isn't called (or is it?) and author's save() is
called before it is linked to the entry.
I think one can update this field in a manipulator or a view but it
requires to remember to do it only this way throughout the project.
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
