Malcolm Tredinnick wrote:
>> Well, if the field is blank and if I said that I'd like to store
>> NULL values in the model definition, I guess I want to store NULL in
>> the database, not empty strings. If that's not the case, I'm
>> probably good for the pshrink. :)
>
> No; in general (in database
Forwarded Message
From: Malcolm Tredinnick <[EMAIL PROTECTED]>
To: Kilian CAVALOTTI <[EMAIL PROTECTED]>
Subject: Re: unique and blank/null
Date: Mon, 10 Jul 2006 09:26:41 +1000
On Sun, 2006-07-09 at 18:33 +0200, Kilian CAVALOTTI wrote:
> On Saturday 08 July 2006
On Saturday 08 July 2006 02:52, Malcolm Tredinnick wrote:
> You cannot store NULL values via the admin interface. The reason for
> this is that a web interface is poorly designed as far as being able to
> differentiate between an empty string and a NULL. If the field is blank,
> which one did you
Right, I noticed this as I was skimming the new posts after sending,
sorry.
Don
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@googlegrou
Whoops. Didn't reply to group automatically (now I discovered some new
and interesting behaviour in the way Evolution prioritises reply
fields).
Forwarded Message
From: Malcolm Tredinnick <[EMAIL PROTECTED]>
To: Kilian CAVALOTTI <[EMAIL PROTECTED]>
Subjec
On Fri, 2006-07-07 at 12:03 -0700, Don Arbow wrote:
> On Jul 7, 2006, at 3:57 AM, Malcolm Tredinnick wrote:
> >>
> >> Actually, with SQLite at least, it seems that multiple NULL values
> >> are
> >> considered non unique.
Could you be a bit more careful when trimming the attribution lines
pleas
On Jul 7, 2006, at 3:57 AM, Malcolm Tredinnick wrote:
>>
>> Actually, with SQLite at least, it seems that multiple NULL values
>> are
>> considered non unique.
NULL is not a value, it is the lack of a value. In database theory,
you cannot compare one NULL against another NULL or against a va
On Friday 07 July 2006 12:57, Malcolm Tredinnick wrote:
> Maybe there is some oddity about your circumstances. Can you post more
> details if you are really seeing NULL values being treated distinctly,
> please?
Actually, it may not been SQLite related, after all. I narrowed the problem to
the w
On Fri, 2006-07-07 at 17:25 +0530, Kenneth Gonsalves wrote:
>
> On 07-Jul-06, at 5:17 PM, Kenneth Gonsalves wrote:
>
> >
> >
> > On 07-Jul-06, at 4:08 PM, Kilian CAVALOTTI wrote:
> >
> >> I created a model with a CharField which has to be NULL in the
> >> database. So I
> >> gave it blank=True,
On Fri, 2006-07-07 at 17:17 +0530, Kenneth Gonsalves wrote:
>
> On 07-Jul-06, at 4:08 PM, Kilian CAVALOTTI wrote:
>
> > I created a model with a CharField which has to be NULL in the
> > database. So I
> > gave it blank=True, null=True and unique=True options. I have to
> > allow NULL
> > va
On 07-Jul-06, at 5:17 PM, Kenneth Gonsalves wrote:
>
>
> On 07-Jul-06, at 4:08 PM, Kilian CAVALOTTI wrote:
>
>> I created a model with a CharField which has to be NULL in the
>> database. So I
>> gave it blank=True, null=True and unique=True options. I have to
>> allow NULL
>> values in the data
On 07-Jul-06, at 4:08 PM, Kilian CAVALOTTI wrote:
> I created a model with a CharField which has to be NULL in the
> database. So I
> gave it blank=True, null=True and unique=True options. I have to
> allow NULL
> values in the database, as well as blank values in admin, but in
> the same
On Fri, 2006-07-07 at 12:38 +0200, Kilian CAVALOTTI wrote:
> Hi all,
>
> I created a model with a CharField which has to be NULL in the database. So I
> gave it blank=True, null=True and unique=True options. I have to allow NULL
> values in the database, as well as blank values in admin, but in
Hi all,
I created a model with a CharField which has to be NULL in the database. So I
gave it blank=True, null=True and unique=True options. I have to allow NULL
values in the database, as well as blank values in admin, but in the same
time, I'd like to be sure that non NULL values are unique.
14 matches
Mail list logo
