are column defaults not supposed to be set by django under postgres?
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
--
looking to buy or sell anything?
try: http://allurstuff.com
it's a classified ads service that
shows on a map where the seller is
(think craigslist + google maps)
plus it's 100% free :)
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
