> I forgot to note before, I've added a patch to #7666 which uses James'
> suggestion of a pristine QuerySet.
Using a "pristine" QuerySet is a bad assumption to make, especially
for those who are using custom managers to properly generate SQL for
non-standard columns, e.g., geometries. The patch
It sounds like what you are looking for is an intermediary model, this
is ticket #6905 I believe, and is currently considered a django beta
maybe-feature, which is to say if it's ready by beta, it's in 1.0 else
it will be afterwords.
On Jul 22, 6:38 am, Mathieu Richardoz <[EMAIL PROTECTED]> wrote
On Tue, Jul 22, 2008 at 7:21 PM, Michael Elsdörfer
<[EMAIL PROTECTED]> wrote:
>
> Previously, get_FIELD_display(), for a blank or unknown value of
> FIELD, return the value unchanged, e.g. say None or an empty string.
>
> After the change, it returns the automatically inserted blank choice
> (---
On Tue, 2008-07-22 at 04:21 -0700, Michael Elsdörfer wrote:
> Previously, get_FIELD_display(), for a blank or unknown value of
> FIELD, return the value unchanged, e.g. say None or an empty string.
>
> After the change, it returns the automatically inserted blank choice
> (---). This is due
Hi,
before I create chaos - is it right to use this milestone for everything
that can not go into 1.0 (like any feature requests that are not on the
list)?
Michael
--
noris network AG - Deutschherrnstraße 15-19 - D-90429 Nürnberg -
Tel +49-911-9352-0 - Fax +49-911-9352-100
http://www.noris.de
