On Mon, Apr 6, 2009 at 4:22 PM, mrts wrote:
>
> On Apr 6, 2:45 am, Jacob Kaplan-Moss
> wrote:
>> Can you please stop? We all get that you think these tickets are
>> important. They're on the milestone for 1.1, so they'll be fixed.
>> Nagging us here doesn't help get your tickets pushed to the fr
On Apr 6, 2:45 am, Jacob Kaplan-Moss
wrote:
> Can you please stop? We all get that you think these tickets are
> important. They're on the milestone for 1.1, so they'll be fixed.
> Nagging us here doesn't help get your tickets pushed to the front of
> the queue.
I'm baffled. From which parts of
On Sun, Apr 5, 2009 at 4:52 PM, mrts wrote:
> [...]
Can you please stop? We all get that you think these tickets are
important. They're on the milestone for 1.1, so they'll be fixed.
Nagging us here doesn't help get your tickets pushed to the front of
the queue.
Jacob
--~--~-~--~~-
First, let me thank Malcolm for promptly fixing #10710. Unfortunately
#10733 is still barring the use of only() and select_related()
properly.
Given the models and admin defined above and the requirements that
* admin changelist view should perform only a single query,
* that should pull in onl
Omission: the models and admin used in experiments have changed a bit
from the original post:
from django.db import models
class Base(models.Model):
name = models.CharField(max_length=10)
lots_of_text = models.TextField()
class Meta:
abstract = True
def __unicode__(self
(Sorry for top-posting, Google Groups is misbehaving.)
Jacob argued on #django-dev that you can already achieve the only()
behaviour by overriding ModelAdmin.queryset().
So I experimented with that. "The results were disappointing," as prof.
Denzil Dexter from The Fast Show used to say :) .
A
