> Wouldn't it make more sense to limit them in the admin or the forms > instead of limiting them right in the models? The act of selecting an > activity topic in a form is form specific, the models don't (and > probably don't need to) have any knowledge of that.
I'm not sure what you're driving at... this isn't about selecting activites, but selecting the cert_type in a participation record. There are many times (like the ForeignKey limit_choices_to parameter), where general model form behavior is indeed set up, rightly, as part of the model. Let me clarify what I'm trying to do here. A participation occurs in the context of its activity, which is represented by its ForeignKey to the activity. Each activity has a ManyToMany denoting the cert_types available for participating in that activity. When I add or change a participation record, I need to select the cert_type requested by the participant. Thus the foreign key to cert_types. However I need to limit the choices available to those in its associated activity. Hmm... now that I think about it, doesn't really seem doable, except in participations inlined with their activity, where the activity is known at render time and not modifiable in the form. Guess I'm going to have to rethink what I'm doing. Thanks, Wayne --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" 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/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
