My impression was that Jeremy had a simple is_artist field in the table the admin generator was administering, which is easy with the standard admin generator filter stuff.
Your impression is that is_artist is in a separate table, joined to the first. You could well be right. Jeremy, it would be helpful to see your schema if you're still listening. But in any case I agree entirely that it would be nice if it were easier to build filters based on information kept in separate tables, such as sfGuardPlugin's sfGuardUserGroup table. You CAN do it - I added a groups filter to sfGuardPlugin and contributed it back just a week ago - but it's a bit hairy. So after reading your email I sat down and wrote a HOWTO based on that experience and added it to the Wiki. Jeremy, if you're dealing with joins, you should check it out: http://trac.symfony-project.org/wiki/HowtoAddCustomFilterCriteria For the symfony devs: that HOWTO includes a short proposal for the future at the end which would be backwards-compatible and make adding custom criteria in the admin generator much easier and safer. -Tom --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "symfony developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/symfony-devs?hl=en -~----------~----~----~----~------~----~------~--~---
