I decided to finally tackle this very old "easy" ticket.
http://code.djangoproject.com/ticket/4092
My updated patch is attached to the ticket. I did not include the
original modifications to ModelChoiceField since that produced
failures in the forms tests and removing the empty_label option fro
One could also set a default ordering on a model and have a consistent
order everywhere :)
--
Collin Grady
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send emai
On Fri, Feb 27, 2009 at 1:21 PM, PauloS wrote:
>
> Hi,
>
> I have a related patch (#10263).
>
> I have an application where I rendered my inline forms like an
> spreadsheet, the effect when the user saves the form and the row order
> changes is very unpleasant. This bug does not show up often bec
Hi,
I have a related patch (#10263).
I have an application where I rendered my inline forms like an
spreadsheet, the effect when the user saves the form and the row order
changes is very unpleasant. This bug does not show up often because
most databases other than Postgres return unordered queri
On Fri, Feb 27, 2009 at 11:45 AM, Øyvind Saltvik
wrote:
>
> Should be doable but you need to filter on a field of the subclass
> being null.
>
> SomeModel.objects.filter(somemodelsubclass__somefield=None) ,
> somefield cannot be id or pk.
That is one method I found, but it seems very incorrect t
Should be doable but you need to filter on a field of the subclass
being null.
SomeModel.objects.filter(somemodelsubclass__somefield=None) ,
somefield cannot be id or pk.
On 27 Feb, 14:13, Calvin Spealman wrote:
> On Fri, Feb 27, 2009 at 1:31 AM, Malcolm Tredinnick
>
>
>
> wrote:
>
> > On Thu,
On Fri, Feb 27, 2009 at 1:31 AM, Malcolm Tredinnick
wrote:
>
> On Thu, 2009-02-26 at 11:08 -0500, Calvin Spealman wrote:
>> I'm looking for the best way to query based on the existence of an
>> instance of a subclass. In my case, there are Actions that have
>> several subclasses, like FriendReque
