On 11/18/06, Scott Paul Robertson <[EMAIL PROTECTED]> wrote:
> On Fri, Nov 17, 2006 at 12:00:02AM -0600, Adrian Holovaty wrote:
> > However, one goal I've had for newforms *is* to let developers
> > manually specify/override the form Field used for any particular
> > database Field in the admin si
On Fri, Nov 17, 2006 at 12:00:02AM -0600, Adrian Holovaty wrote:
> However, one goal I've had for newforms *is* to let developers
> manually specify/override the form Field used for any particular
> database Field in the admin site. I think this could be achieved with
> a hook in the "class Admin".
On 11/17/06, Jani <[EMAIL PROTECTED]> wrote:
> Is there any reason not to use same argument names in database fields
> and form fields? I have been playing with newforms and I constantly
> write "max_length" argument in CharField as "maxlength" which is used
> in database and oldforms CharField.
Is there any reason not to use same argument names in database fields
and form fields? I have been playing with newforms and I constantly
write "max_length" argument in CharField as "maxlength" which is used
in database and oldforms CharField.
Jani
--~--~-~--~~~---~-
On 11/16/06, SmileyChris <[EMAIL PROTECTED]> wrote:
> It seems like a great opportunity as newforms develops to clean up the
> database fields mess. Most of the arguments you pass a database field
> are not related to the database.
>
> Is this part of the goal of newforms, or am I thinking too big
It seems like a great opportunity as newforms develops to clean up the
database fields mess. Most of the arguments you pass a database field
are not related to the database.
Is this part of the goal of newforms, or am I thinking too big?
With newforms, we can just have one optional argument (for
