2007/10/24, Derek Anderson <[EMAIL PROTECTED]>: > > are column defaults not supposed to be set by django under postgres? yes, correct defaults are never set by django for postgres are they set for other databases? don't know why it's so.
> see: > > $ ./manage.py sql auth > BEGIN; > [...] > CREATE TABLE "auth_user" ( > "id" serial NOT NULL PRIMARY KEY, > "username" varchar(30) NOT NULL UNIQUE, > "first_name" varchar(30) NOT NULL, > "last_name" varchar(30) NOT NULL, > "email" varchar(75) NOT NULL, > "password" varchar(128) NOT NULL, > "is_staff" boolean NOT NULL, > "is_active" boolean NOT NULL, > "is_superuser" boolean NOT NULL, > "last_login" timestamp with time zone NOT NULL, > "date_joined" timestamp with time zone NOT NULL > ); > [...] > COMMIT; > > where: > is_staff = models.BooleanField(..., default=False, ...) > is_active = models.BooleanField(..., default=True, ...) > is_superuser = models.BooleanField(..., default=False, ...) > > they're also not set under my own models: > > class Poll(models.Model): > question = models.CharField(maxlength=200, default='test') > > CREATE TABLE "case02_rename_field_poll" ( > "question" varchar(200) NOT NULL, > ); > > thanks, > derek -- Best regards, Yuri V. Baburov, ICQ# 99934676, Skype: yuri.baburov, MSN: [EMAIL PROTECTED] --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
