> I find an orm usefull for 3 scenarios:
> 1. - simple object retrieval posts.objects.all()
> 2. - performance optimized object retrieval, your raw approach would
> suffice here
> 3. - generating complex queries, and reusing sql components
> When you get to complex data models, Django currently fa
Thanks for your feedback.
I appreciate it.
I find an orm usefull for 3 scenarios:
1. - simple object retrieval posts.objects.all()
2. - performance optimized object retrieval, your raw approach would
suffice here
3. - generating complex queries, and reusing sql components
When you get to complex
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 optimization
>> django orm doesn't suffice. Its a pity to see s
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 orm, while at the same time the
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 doesn't suffice. Its a pity to see st
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
