Hi,
On Thursday, January 17, 2013 11:08:01 PM UTC+1, Russell Keith-Magee wrote:
>
> So - while I'm not sure there's a place for this in core (unless you can
> demonstrate how to implement range types on other backends), it should be
> *possible* to use this library as a third party extension. If
On Thu, Jan 17, 2013 at 10:08 PM, Russell Keith-Magee
wrote:
> The other thing I'd suggest is to look at others doing similar work. For
> example, Zachary Voase has been working on extensions to Django's PostgreSQL
> backend to support a whole lot of extra PostgreSQL features[1]. From the
> look o
On 18 tammi, 13:00, Florian Apolloner wrote:
> Hi,
>
> On Thursday, January 17, 2013 11:08:01 PM UTC+1, Russell Keith-Magee wrote:
>
> > So - while I'm not sure there's a place for this in core (unless you can
> > demonstrate how to implement range types on other backends), it should be
> > *pos
Can someone who's familiar with Django internals please confirm or deny the
following answer to my question?
http://stackoverflow.com/a/14369747/76701
Thanks,
Ram.
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To view this discussion
Hi Ram,
On 01/18/2013 06:25 AM, Ram Rachum wrote:
> Can someone who's familiar with Django internals please confirm or deny
> the following answer to my question?
>
> http://stackoverflow.com/a/14369747/76701
That answer is correct. A common situation for evaluating a queryset in
a boolean conte
On 17/01/2013 22:08, Russell Keith-Magee wrote:
On Mon, Dec 31, 2012 at 5:56 PM, Marco Paolini mailto:markopaol...@gmail.com>> wrote:
Hi all,
sorry for the noise, forget my previous mail as it was pointing to the
wrong commit,
here's the good one:
https://github.com/mpaolini
On 18/01/2013 12:55, Anssi Kääriäinen wrote:
On 18 tammi, 13:00, Florian Apolloner wrote:
Hi,
On Thursday, January 17, 2013 11:08:01 PM UTC+1, Russell Keith-Magee wrote:
So - while I'm not sure there's a place for this in core (unless you can
demonstrate how to implement range types on oth
On 18 tammi, 17:35, Marco Paolini wrote:
> > For examples of how to define lookups, see:
> >https://github.com/akaariai/django/compare/ticket_16187_new#L13L72and
> > the Lookup object itself
> > athttps://github.com/akaariai/django/compare/ticket_16187_new#L6R50.
> > Warning about the code - it w
Thanks Carl!
I suggest copying your explanation into the documentation.
Thanks,
Ram.
On Fri, Jan 18, 2013 at 5:26 PM, Carl Meyer wrote:
> Hi Ram,
>
> On 01/18/2013 06:25 AM, Ram Rachum wrote:
> > Can someone who's familiar with Django internals please confirm or deny
> > the following answer
On Fri, Jan 18, 2013 at 10:58 AM, Ram Rachum wrote:
> I suggest copying your explanation into the documentation.
it's already there:
" This means that calling QuerySet.exists() is faster than
bool(some_query_set), but not by a large degree. If some_query_set has
not yet been evaluated, but you k
It's done more like explaining a side-effect than explaining the *purpose* of
the method. It shouldn't be "notice that when you use `exists`, it has the
following effects on efficiency", but "`exists`'s entire purpose is to get
higher efficiency in situations where you don't want to access the data
11 matches
Mail list logo
