On 10/9/07, Brian Rosner <[EMAIL PROTECTED]> wrote:
>
> On 2007-10-09 14:39:57 -0600, "Joseph Kocherhans" <[EMAIL PROTECTED]> said:
>
> >
> > On 10/9/07, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:
> >>
> >> This raises some alarm bells. Why on earth are we futzing around in
> >> ChangeManipulat
At 07:11 PM 10/9/2007, Brian Rosner wrote:
>Your wish is my command ;)
>
>http://code.djangoproject.com/ticket/5720
Wow, that was fast. I can confirm this patch makes bringing up the
change form for my problematic model nice and zippy. Thanks!
I did run into another problem -- instances of t
On 2007-10-09 14:39:57 -0600, "Joseph Kocherhans" <[EMAIL PROTECTED]> said:
>
> On 10/9/07, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:
>>
>> This raises some alarm bells. Why on earth are we futzing around in
>> ChangeManipulators here? They are entirely oldforms-related and the
>> whole poi
On 10/9/07, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:
>
> This raises some alarm bells. Why on earth are we futzing around in
> ChangeManipulators here? They are entirely oldforms-related and the
> whole point is to remove any reliance on them.
>
> This might well be a bug and in an area that
On Tue, 2007-10-09 at 15:56 -0400, Karen Tracey wrote:
> I tried out the newforms-admin branch for my app today. The
> conversion went fine, except for a performance problem with the new
> raw_id_fields. As background, I have a model with two ForeignKey
> fields (among other stuff). The numb
5 matches
Mail list logo