Re: MySQL index hints

On Fri, Jul 16, 2010 at 10:43 AM, Simon Litchfield wrote: > Russ -- > > Firstly, re namespacing. No worries, let's just keep it RDBMS- > specific, ie -- > > MySQL - with_hints(use={}, force={}, ignore={}) > Oracle - with_hints(index={}, ...) > > That gives plenty of name

Ticket #13844 - Errors when using character fields for aggregation

I wanna to call attention to this bug. When using a aggregate in a CharField, we get a value_error because returned value are cast to float, so a single query like Link_A.objects.all().aggregate(Max('short_link')) raise value error and need to be done with connection.cursor().execute(...). All

Re: memcached-based-cache - timeout=0 does not work as intended by memcached

On Thu, Jul 22, 2010 at 10:43 AM, Alex Gaynor wrote: > On Wed, Jul 21, 2010 at 9:41 PM, Russell Keith-Magee > wrote: >> On Fri, Jul 16, 2010 at 6:54 PM, Carsten Reimer >> wrote: >>> Hello, >>> >>> I am not quite

Re: memcached-based-cache - timeout=0 does not work as intended by memcached

On Wed, Jul 21, 2010 at 9:41 PM, Russell Keith-Magee wrote: > On Fri, Jul 16, 2010 at 6:54 PM, Carsten Reimer > wrote: >> Hello, >> >> I am not quite sure if this is the right mailinglist but as long as my >> remarks are about a

Re: memcached-based-cache - timeout=0 does not work as intended by memcached

On Fri, Jul 16, 2010 at 6:54 PM, Carsten Reimer wrote: > Hello, > > I am not quite sure if this is the right mailinglist but as long as my > remarks are about a core-component of django I hopefully chose the right > list. > > Dealing with cache-stuff in Django I

Re: proposal: abstract file upload/download handling

On Sun, Jul 18, 2010 at 1:59 AM, Waldemar Kornewald wrote: > Hi Russell, > so, after our chat on IRC I've finally found the time to implement a > real proposal including unit tests. I've attached the patch to this > ticket: > http://code.djangoproject.com/ticket/13960 > >

Re: filtering aggregation without filtering objects

That makes sense. While my proposal isn't made for a sake of proposing something, I see that I hardly can speed up implementing it without following your last advice and working on other Django ORM issues. I'm going to find out what I can do. Thanks. -- Best Regards, Valentin Golev Lead

Re: filtering aggregation without filtering objects

On Wed, Jul 21, 2010 at 6:02 PM, Valentin Golev wrote: > Thanks for your reply. > > 'You have SQL, go write some, our ORM already contains everything what > Django needs' - that's what you say, am I getting it right? I'm > confused by your answer. But I can't argue with that,

Re: filtering aggregation without filtering objects

Thanks for your reply. 'You have SQL, go write some, our ORM already contains everything what Django needs' - that's what you say, am I getting it right? I'm confused by your answer. But I can't argue with that, if it's Django strategy, well, I have to respect it. You said that's extending ORM

Re: filtering aggregation without filtering objects

I like screwing these counters to model try something like that. class RegistrationProfile(models.Model): """ A simple profile which stores an activation key for use during user account registration. Generally, you will not want to interact directly with instances of this

Re: filtering aggregation without filtering objects

On Wed, Jul 21, 2010 at 1:17 AM, Valentin Golev wrote: > Hello, > > There is a common situation for almost all of my projects. Maybe it's > my mistake somewhere, maybe Django really lacks of some ability. > > Let's suppose a simple structure: > > model User; > model Message (