First of all, welcome to Django!

While many like to use the admin as a public facing CRUD app, that is not
what it is designed for. In any case, writing your own forms is *a
requirement* in pretty much every Django project, simply because no
automatic form creation like the admin could possibly anticipate the
infinite number of use cases and workflows.

Think of the admin as something to help you get some data in the database
fast, and manually edit rows in the future, not as the catch all solution
to your users interactions with the product.

When you learn to tweak the admin, you learn a lot about a very
unconventional app and a little about the framework. The "magic" of that
built-in app is also what makes the complexity of modifying it grow
exponentially as the particularity of your needs increase.

If you on the other hand decide to dive into forms, signals, middleware,
asynchronous tasks, class based views and serialization, you learn all the
good stuff and the sky is the limit. And we'll be glad to help you through
the entire way!

Good luck and happy coding!

Cheers,
AT

On Dec 29, 2011 12:57 PM, "Bart Nagel" <b...@tremby.net> wrote:
>
> At 2011-12-28 06:59:31 -0800, Jay De Lanoy wrote:
> > I'd go for a separate table instead, with something like
> >
> >     class BillingInfo(models.Model):
> >         customer = models.OneToOneField(Customer)
> >         billing_address = models.OneToOneField(Address)
> >
> > and then just have logic in the views and templates to account for
> > existence/nonexistence of a given customer's billing address.
>
> Would this approach mean implementing my own forms to populate
> customers and addresses and not using the built-in Django admin forms
> at all? They were a major draw for me to Django.
>
> Thanks.
>
> --bart
>
> --
> 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.
>

-- 
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.

Reply via email to