On Fri, 2009-01-23 at 00:12 -0800, Evgeniy Ivanov wrote: > On Jan 23, 3:17 am, Malcolm Tredinnick <malc...@pointy-stick.com> > wrote: > > Addressing this only in the admin would be short-sighted, however. A for > > field that new how to handle reverse relations would be the first step > > and then allowing the admin to use that is the second one. > > > > Maybe better approuch is in model's meta? It will give forms a chance > to do this fancy thing. And it is a kind of logical, since model > really has such relation.
No. Because Meta is not about presentation. It's part of the model, which is defining how the data is stored and retrieved. This whole issue is *purely* presentational. Attempting to change the model class to "solve" it is simply using the wrong shovel to hammer in your screws. Regards, Malcolm --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
