Ok - gotcha. Yes, I think I've come full circle now! At the time I
started this thread I had moved away from the modelFormSet and back to
teh regular formset. Using the regular formset and my own logic I can
identify which forms go with actual instances and which require
instances to be created. So that does work. I just somehow got bound
and determined to make the modelFormSets work - but I think that's not
meant to be.
I do think that a nice model would be to allow initial data and
querysets to work together in the modelFormSet. For example, suppose
you had a queryset containing 5 items and you wanted 8 forms, with the
first 5 mimicing the existing 5 instances and the last 3 being created
from initial data. It seems like a nice intuitive user interface
would be to create initial data for all 8 instances, possibly with the
first 5 being empty dicts, and the last 3 containing your initial
data. In other words, in order to provide your initial data for the
last 3, you would have to provide initial data for all, so you wold
just provide "empty" intiial data. Then the next step would for the
modelformset to be able identify that when you save each of the forms,
that the first 5 save to the existing 5 instances provided in the
queryset and that the last 3 save to new instances. Obviously a big
source change, just throwing it out there in case there s work in this
area in the future.
Anyway, thanks for all the clarification. I definitely learned a lot
in the process of debugging this all and I think I know enough to be
able to work this out using the standard formsets.
Margie
On Mar 4, 8:15 pm, Malcolm Tredinnick <malc...@pointy-stick.com>
wrote:
> On Wed, 2009-03-04 at 19:47 -0800, Margie wrote:
> > Yes, I agree with what you are saying about self._initial_form_count
> > being set to a number greater than zero due to me using initial in my
> > code that creates the formset, as follows:
>
> > def makeTaskDetailFormSetForCreate(tileList, data=None):
> > TaskDetailFormSet = modelformset_factory(TaskDetail,
> > form=TaskDetailForm,
>
> > formset=TaskDetailCustomBaseFormSetForCreate)
>
> > taskDetailFormSet = TaskDetailFormSet(data=data,
> > tiles=tileList,
> > initial=[{"tile":tile.id}
> > for tile in tileList])
>
> > return taskDetailFormSet
>
> > But if I don't use initial - how do I create the initial values for
> > the forms? I thought using initial is the "right" way to do it?
>
> I mentioned before that initial data doesn't necessarily make sense for
> new models in a modelformset, in some ways (in other ways it does -- but
> it's not really practical to handle every single possibility, so
> sometimes you just have to deal with it). The thing is that initial data
> always results in a populated form -- so data is submitted and a new
> entry will be created. That doesn't work for "extra" forms, in the
> formset sense, where you're only going to enter new data and, if you
> don't, they won't have any effect on things.
>
> If you really, really want to prepopulate fields and can also have some
> way to work out whether the data is "new" or the "initial" stuff, then
> you'll be able to use it, but you'll have to do some of the form
> handling yourself. Reading the source and thinking very hard about
> things is the solution to that problem. I'm sure it's possible, but it
> will take some thinking. At some point, you just have to say it's not a
> standard modelformset case and let go of that particular aid.
>
> 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
-~----------~----~----~----~------~----~------~--~---
