2011/2/10 :
...
Thanks for the kind words. Your comments are very welcome!
--
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@googlegroups.com.
To unsubscribe from this group, send email to
django
On Thu, 10 Feb 2011 14:27:18 +0100, Roman Klesel
wrote:
> 2011/2/10 :
> '' == None
>> False
>
> yes, makes sense ... I was thinking of things like:
>
> if '':
> if []:
> ...
>
> which probably lead me to a wrong conclusion.
I apologize for the previous message being a bit rude.
Python is
2011/2/10 :
'' == None
> False
yes, makes sense ... I was thinking of things like:
if '':
if []:
...
which probably lead me to a wrong conclusion.
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to djan
>> You explicitly set the field to an empty string,
>
> Yes, which evaluates to an equivalent of None or False in python, and
> with the above setting I've declared that None values should be
> allowed and should be stored as NULL in the database.
Python 2.6.5 (r265:79063, Apr 16 2010, 13:57:41
Hello Daniel,
thanks for you reply
2011/2/10 Daniel Roseman :
>> >>> from test_django.roman.models import Jtem
>> >>> o=Jtem.objects.get(pk=29)
>> >>> o.name=''
>> >>> o.save()
>>
>> Now the record looks like this:
>>
>> mysql> select * from roman_jtem where id=29;
>> ++--+--+
>>
On Thursday, February 10, 2011 10:19:49 AM UTC, Roman Klesel wrote:
>
> Hello community,
>
> I'm using a django version 1.3 beta 1 SVN-15481 and a mysql 5 backend
>
> I have the following field definition in my model:
>
> class Jtem(models.Model):
> name=models.CharField(blank=True, null=True,
6 matches
Mail list logo