In ticket #8576 a request was made to remove the restriction that
AutoFields must be primary keys so that multiple AutoFields could be
used in a model. In MySQL multiple auto-increment fields does not
make sense and probably does not make sense in any other database.
However, I do think the case
Of course not - you can do .order_by() to clear ordering if you really
don't want a default ordering somewhere, but all your examples sound
like you do :)
On Sat, Feb 28, 2009 at 3:02 PM, PauloS wrote:
>
> On Feb 27, 5:28 pm, Collin Grady wrote:
>> One could also set a default ordering on a mod
On Sat, Feb 28, 2009 at 6:34 PM, PauloS wrote:
>
> InlineFormSet is perfect to build spreadsheet-like grid interfaces,
> but for a good user experience the form elements need to have
> consistent order across GET-after-POST cycles. Currently this happens
> BY ACCIDENT in most SGBD backends, and I
InlineFormSet is perfect to build spreadsheet-like grid interfaces,
but for a good user experience the form elements need to have
consistent order across GET-after-POST cycles. Currently this happens
BY ACCIDENT in most SGBD backends, and I think relying on accidents is
bad programming style.
The
On Feb 27, 5:28 pm, Collin Grady wrote:
> One could also set a default ordering on a model and have a consistent
> order everywhere :)
This way you have to pay the ORDER BY price for every query?
--~--~-~--~~~---~--~~
You received this message because you are subs
Not being a part of the developers, but being interested in the proper
resolution of this feature, I just second this request: somewhen this
just should be dealt with.
My own understanding is that lacking a stock BigInt field (or some
stock customization capability of the Integer field that would
If anything I think SomeModel.objects.filter(somemodelsubclass=None)
makes more sense.
May be worth filing a ticket.
On 27 Feb, 18:25, Calvin Spealman wrote:
> 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
>
2009/2/27 Collin Grady
>
> One could also set a default ordering on a model and have a consistent
> order everywhere :)
>
I personally agree with this one, the issue at hand is because of 'bad
programming' in my opinion and shouldn't be solved internally by django
(certainly if the fix isn't tri
On Feb 27, 12:25 pm, Calvin Spealman wrote:
> On Fri, Feb 27, 2009 at 11:45 AM, Øyvind Saltvik
> > 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 o
