ok
On 1/12/14, Tim Graham wrote:
> Please don't crosspost to both django-developers and django-users. The
> topic of this list is the development of Django itself, django-users is for
>
> usage questions, although it's not clear to me how this question is related
>
> to Django.
>
> On Saturday, J
I'm doing some work on the docs, keeping the same basic structure of the
document to start with and tidying up the formatting and the language. I've
read through the code and it looks sane, just a couple of small comments.
On 12 January 2014 08:51, Anssi Kääriäinen wrote:
> The lookup system re
On Sunday, January 12, 2014 10:52:03 AM UTC+2, Josh Smeaton wrote:
>
> Any idea how to do this?
>>
>> The new way in custom lookups is trying to first call as_vendorname(qn,
>> connection), if that doesn't exist then call the standard implementation,
>> that is as_sql(). For example on sqlite Dja
The lookup system refactoring is nearly ready. The work is tracked in
ticket https://code.djangoproject.com/ticket/16187 and latest patch can be
found from https://github.com/django/django/pull/2019.
I need help to get the pull request finalized. The ways to help are:
- Improve the documentati
>
> Any idea how to do this?
>
> The new way in custom lookups is trying to first call as_vendorname(qn,
> connection), if that doesn't exist then call the standard implementation,
> that is as_sql(). For example on sqlite Django will first try to call
> as_sqlite(), if that doesn't exist then
On Saturday, January 11, 2014 10:06:14 AM UTC+2, Josh Smeaton wrote:
>
>
>- Custom backend implementation of aggregates and annotations
>
> Any idea how to do this?
The new way in custom lookups is trying to first call as_vendorname(qn,
connection), if that doesn't exist then call the standar
