Waylan Limberg wrote: > For an example of how the admin app does this see search_fields > http://www.djangoproject.com/documentation/model_api/#search-fields > > -- > ---- > Waylan Limberg > [EMAIL PROTECTED]
Yes, I guess I could split the text entered and then do a search for each word in both first_name and last_name like the admin interface does... just seems like this would return many more results than wanted with a large user group. 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? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
