On Fri, 2009-01-16 at 01:33 -0800, Evgeniy Ivanov (powerfox) wrote: > > > On Jan 16, 5:16 am, Malcolm Tredinnick <malc...@pointy-stick.com> > wrote:
[...] > > You need to go back and look at your original problem. You wanted forms > > with multiselect fields for both forms. So the real question is "how do > > you do that". I suspect the answer is that you have to manually > > construct one of the forms (which you can write a helper function to do > > if you need this in a lot of projects, or, if this only happens for one > > model, just write a single form class). > > Thanks, will try. Current sollution (create table manually and specify > name/columns) is neither right or cute. I think part of the conceptual problem here is that you're trying to solve your problem by working on the model definition. But the problem is a form issue. It's about presentation, not data storage. So approach it from that end. Regards, Malcolm --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
