On Sun, Oct 4, 2009 at 5:00 AM, James Bennett wrote:
>
> On Sat, Oct 3, 2009 at 1:58 PM, Thierry wrote:
>> I know this is not a problem for most users. But when working with
>> complex projects or projects requiring some performance
On Sat, Oct 3, 2009 at 1:58 PM, Thierry wrote:
> I know this is not a problem for most users. But when working with
> complex projects or projects requiring some performance optimization
> django orm doesn't suffice. Its a pity to see strong development on
> django
On Sat, Oct 3, 2009 at 2:58 PM, Thierry wrote:
>
> http://code.djangoproject.com/wiki/Version1.2Features
>
> I know this is not a problem for most users. But when working with
> complex projects or projects requiring some performance optimization
> django orm
http://code.djangoproject.com/wiki/Version1.2Features
I know this is not a problem for most users. But when working with
complex projects or projects requiring some performance optimization
django orm doesn't suffice. Its a pity to see strong development on
django orm, while at the same time the
I haven't looked hard at the fix, but I hit the bug a lot and agree
that it would be great if this was fixed :)
On Oct 4, 3:12 am, Carl Meyer wrote:
> Anyone have thoughts on this? It would be really nice to get this
> fixed so admin.py errors don't break the runserver,
Anyone have thoughts on this? It would be really nice to get this
fixed so admin.py errors don't break the runserver, and I think the
updated patch on #11957 accomplishes this without any breakage.
Carl
On Sep 28, 4:56 pm, Carl Meyer wrote:
> Today I filed #11957 [1],