On Friday, February 22, 2013 11:27:59 PM UTC-7, Skylar Saveland wrote:
>
> This is still a good question :)
>
The answer is that there is no way to instruct Django that you really,
truly want this CharField to be NOT NULL even on Oracle, and that is
unlikely to change. Part of the philosophy
This is still a good question :)
On Thursday, March 11, 2010 5:57:13 AM UTC-8, Wayne wrote:
>
> Hi Karen,
>
> Many thanks for your reply.
> Now our business requirements do not allow either empty string or null
> value for this particular charField column (name =
>
Hi Karen,
Many thanks for your reply.
Now our business requirements do not allow either empty string or null
value for this particular charField column (name =
models.CharField(max_length=512, null=False, blank=False)). How do you
suggest we should configure this field so that we can enforce not
On Fri, Feb 26, 2010 at 5:35 PM, Wayne wrote:
> Hi,
> I try to create tables using Django models in our test oracle
> database. I define a model with one column like this: name =
> models.CharField(max_length=512, null=False, blank=False). After
> running python manage.py
Hi,
I try to create tables using Django models in our test oracle
database. I define a model with one column like this: name =
models.CharField(max_length=512, null=False, blank=False). After
running python manage.py syncdb, I found that column 'name' in the
generated table still allows null value
5 matches
Mail list logo