Hi folks!
Any news about this ticket: https://code.djangoproject.com/ticket/10164 ?
I am having this issue using SQLite3 in django 1.5. The primary key is
not monotonic
increasing.
Leonardo
--
You received this message because you are subscribed to the Google Groups
"Django developers" group
Hi Warren,
On 08/26/2013 03:32 PM, Warren Smith wrote:
> Any chance that https://code.djangoproject.com/ticket/20693 can make it
> into 1.6?
Thanks for your work on the patch! Since it's a new feature, it's a
couple months late for 1.6; it would have needed to go in before the
first 1.6 beta was
Any chance that https://code.djangoproject.com/ticket/20693 can make it
into 1.6?
It has been sitting in ready-for-checkin for several weeks now. I thought I
had done everything I could, but then I realized that my branch was out of
date and it was skewing the diff on
https://github.com/django/dja
Please ask questions about using Django on django-users. The topic of this
list is development of Django itself.
Thanks,
Karen
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To unsubscribe from this group and stop receiving emails from it
Is it adviseable to create a customer Auth user or extend the built in
auth.User model to accomodate some additional information.
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To unsubscribe from this group and stop receiving emails from
Just a small note, I've done a small prefetch framework (mind you, before
prefetch_related was implemented) here:
https://github.com/ionelmc/django-prefetch
It allows you to have a tailored prefetching process. It's a bit low level
but it supports all the scenarios you mentioned. If you think i
On Friday, August 23, 2013 11:25:42 AM UTC-4, Andrew Ingram wrote:
> Essentially, I'm wondering if extending the prefetch_related concept is
> the right approach, and whether it's instead worth exploring the more
> general idea of "attaching stuff to models at the ORM level". There're a
> lot o
I think that restriction is reasonable.
So this wouldn't work:
Publisher.objects.prefetch_related('authors', to_attr='authors_by_age',
queryset=Author.objects.order_by('age')).prefetch_related('
authors_by_age__books')
But this would:
Publisher.objects.prefetch_related('authors').prefetch_related(
On Friday, August 23, 2013 6:03:13 PM UTC+3, Marc Tamlyn wrote:
>
> Ticket #17001 concerns the ability to customise the querysets used when
> using `prefetch_related()`. This has a working implementation with a less
> than ideal API - see the patches on the ticket.
>
> As the API design seems to
