On Thu, Jan 8, 2009 at 12:28 AM, Glen Jarvis <g...@glenjarvis.com> wrote:
> I'm not certain if this is a bug, or expected behavior. It certainly looks > like a Django bug to me. However, after looking at the same database for > hours on end, it could simply be a cross-eyed user error. > > In sort, the admin interface has the following search fields (I know this > won't scale very well and is cumbersome. Unfortunately, it's the fields my > customer wants to search; I also know that the first_service, > second_service, etc. models breaks 2nd normal form.... however, again, it is > my customer's preference =( ). > > search_fields = ['contact_name', 'alternate_contact_name', > 'cross_reference', 'client_reference', 'info', > 'people_involved__first_name', 'people_involved__last_name', > 'people_involved__info', 'case_notes__notes', > 'first_service__service', 'second_service__service', > 'third_service__service', 'fourth_service__service', > 'first_subcontractor__subcontractor', > 'second_subcontractor__subcontractor', > 'third_subcontractor__subcontractor', > 'fourth_subcontractor__subcontractor' > ] > > > If you look at the following link, you'll see two 'cases': > > http://barbados.thepythonshoppe.com/forensic/admin/forensic_database/case/ > > userid: admin > password admin > > (this is a development instance for testing) > > If you notice in case 1, you'll notice that 'indigo' is a 'Person Involved' > first name set up for testing. However, it is not found during a search. In > summary, the following search fields work perfectly: > * 'contact_name' > * 'alternate_contact_name' > * 'cross_reference' > * 'client_reference' > * 'info' > > While the remainders do not. Either I am not properly using the syntax of > 'model, double underscore, field' to refer to the foreign model, I've made > another mistake (or am missing a key piece of information), or this is a > legitimate bug (i.e., foreign key lookups do not work). > > Any help you can give would be great. Then I would know that I need to go > read something to learn from a mistake, or I need to break this down into a > test case for a bug reproduction. > > I've tested this against the latest trunk with the same results. > > The admin.py file is attached. > > Thanks in advance, > I'd expect to get an error (I know I've gotten them) if the double-underscore syntax were incorrect or if you were specifying non-existent fields, etc. ForeignKey spanning search such as this does work -- I just tried adding some to my DB (using both forward and backwards relationships) and they worked correctly, even when more than five were listed in a single search_fields list. So I have no idea what is going wrong in your case. I'd try simplifying search fields to a single one that is not currently working. If you specify that one, does it work? If not, check the SQL generated by the admin (either turn on query logging at the database or use something like the debug toolbar) for clues as to why the search isn't working. If the one field does work, add fields one at at time until it breaks, and see what sort of clues you get then, and from the SQL generated then, etc. Karen --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
