If you are already add/deleting in place using ajax you can use that to
your advantage. Don't think of it as a single form - each ajax capable
component (profile, extra1, extra2, extra3) is a separate form. You have a
view that populates your template with multiple forms - the profile and
each
On Friday, April 8, 2016 at 11:27:01 AM UTC-7, Tundebabzy wrote:
>
> I don't know if I'm off target but.
>
> I'm presently work on something like this where I have have to save three
> models at a go. One model is a stand alone while the other two have a
> foreign key to the stand alone
I don't know if I'm off target but.
I'm presently work on something like this where I have have to save three
models at a go. One model is a stand alone while the other two have a
foreign key to the stand alone model which is a many to one relationship.
So to implement the many to one where I
I need to build a pretty complex / non-standard form and am looking for
advice on the overall architecture. Consider the following models:
class UserProfile(User):
... standard set of fields
class ProfileExtra():
ForeignKey(UserProfile)
extratype (e.g. skill, work experience, website,
4 matches
Mail list logo
