Bjørn Stabell wrote:
> I do remember posting a comment on the Django docs site about
> mod_python and mpm-worker crashes a while ago, but I cannot find it on
> the Django site anymore.
>
> In any case, we were using mod_python 3.1.3-3. I'm happy to hear it's
> been fixed in 3.2.8.
On 8/24/06, Bill de hÓra <[EMAIL PROTECTED]> wrote:
>
> I gather this proposal means validation will be highly optimised for web
> forms and available only on POST? I understand that is the mainline use
> case, but I have a preference something that wasn't baked into HTML 'cos
> I'll have to hack
James Bennett wrote:
> On 8/23/06, Adrian Holovaty <[EMAIL PROTECTED]> wrote:
>> Thoughts/comments/suggestions on Joseph's plan below, and on Brant's
>> plan in Trac?
>
> I think Brant's rocking the sexiness; the concept of validation
> behaving as a try/except block feels nice to me. And
On Aug 24, 2006, at 2:14 PM, mediumgrade wrote:
> Don't know if this is a Django question or not, but here is the
> situation:
>
> I am developing an application for a client who is a automobile
> broker.
> He wants agents to submit requests for vehicles from the web. The
> agent
> will be
On 8/24/06, Jacob Kaplan-Moss <[EMAIL PROTECTED]> wrote:
>
> Al-rightly then... thoughts?
>
+1 ValidationErrors with an s, as I've said before: the more errors
returned at once, the better.
My problem with Joseph's proposal is that I believe it to be too tied
to the concept of the Model.
James Bennett wrote:
> On 8/24/06, JP <[EMAIL PROTECTED]> wrote:
> > I like James Bennetts's example a lot, but I'd like it more if the form
> > class were ModelForm, descending from a more general Form class that
> > would look much like the base Manipulator class of today.
>
> I think you're
On 8/24/06, Ivan Sagalaev <[EMAIL PROTECTED]> wrote:
>
> Brantley Harris wrote:
> > Maybe it's a philosophic question, but I see it best
> > defined in the "model" space because then it provides a modular
> > process for views to leverage.
>
> Manipulators can (and do) serve not only as model
On 8/24/06, JP <[EMAIL PROTECTED]> wrote:
> I like James Bennetts's example a lot, but I'd like it more if the form
> class were ModelForm, descending from a more general Form class that
> would look much like the base Manipulator class of today.
I think you're confusing me with someone else...
Dan Watson wrote:
> Actually that was one of my favorite pieces. I think it captures what's
> going on in a very intuitive way: try to create/update, if that fails,
> redisplay with errors.
I think the piece on which I agree with JP is that a _form_ serving as
an exception is counter-intuitive.
The tutorial says and mentions that it creates indexes explicitly.
The syncdb command runs the sql from 'sqlall' on your database for all
apps in INSTALLED_APPS that don't already exist in your database. This
creates all the tables, initial data and indexes for any apps you have
added to your
Yes, that worked.
But the documentation always seems to recommend running ./manage.py
syncdb after you set up your models. It should also create any indexes
you have defined.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the
> I'm afraid that I find the idea in Brantley Harris's proposal of
> raising a Form as an exception as a form of flow control really
> counter-intuitive. Apologies and it's just my opinion of course, but it
> has a sort of "too clever" feel to me. Also, exceptions are very
> expensive, and I
I agree and disgree. :)
I like James Bennetts's example a lot, but I'd like it more if the form
class were ModelForm, descending from a more general Form class that
would look much like the base Manipulator class of today.
I'm afraid that I find the idea in Brantley Harris's proposal of
raising
Brantley Harris wrote:
> Maybe it's a philosophic question, but I see it best
> defined in the "model" space because then it provides a modular
> process for views to leverage.
Manipulators can (and do) serve not only as model savers. They can
authorize, register, send mail etc. Manipulator is
On 8/24/06, Brantley Harris <[EMAIL PROTECTED]> wrote:
> No, watch for the difference between a ValidationError being raised
> and a Form exception being raised. In the ValidationError case, it
> must be saved and returned with the other validation errors in the
> given step (1. conversion; 2.
On 8/24/06, James Bennett <[EMAIL PROTECTED]> wrote:
>
> On 8/23/06, Brantley Harris <[EMAIL PROTECTED]> wrote:
> > The problem is that to make it usefull to the user (read: api-user /
> > developer), you have to put the model save in a try / except block so
> > that if there is a validation
16 matches
Mail list logo
