On 21 Paź, 19:20, "Thomas B. Higgins"
wrote:
> Using the SVN trunk version of Django, I have observed that if a model
> IntegerField or FloatField is changed by adding "null=True" syncdb
> does not update the Not NULL property of the column using PostgeSQL
> 8.4. Is this correct behavior, or a b
On Wed, Oct 21, 2009 at 1:20 PM, Thomas B. Higgins wrote:
>
> Using the SVN trunk version of Django, I have observed that if a model
> IntegerField or FloatField is changed by adding "null=True" syncdb
> does not update the Not NULL property of the column using PostgeSQL
> 8.4. Is this correct be
Using the SVN trunk version of Django, I have observed that if a model
IntegerField or FloatField is changed by adding "null=True" syncdb
does not update the Not NULL property of the column using PostgeSQL
8.4. Is this correct behavior, or a bug? The two easy workarounds are
(1) drop the table usi
3 matches
Mail list logo