Gary Wilson wrote:
> Am I correct that it is good database-design practice to not store > derived or calculated fields in your database (e.g. full_name when you > have first_name and last_name)? How then do you go about querying a > derived field? I believe that people often use 'indexed views' i.e. a view that contains a derived column, and having an index on it allows it to be queried quickly. Not sure how that translates into Django's ORM - I think it might depend on whether the view is updatable. Luke --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
