ah, ok. danke.
Jacob Kaplan-Moss wrote:
> On 10/23/07, Derek Anderson <[EMAIL PROTECTED]> wrote:
>> are column defaults not supposed to be set by django under postgres?
>
> Django doesn't set defaults in the database at all.
>
> The basic reason is that too many defaults simply couldn't be
> r
i had thought they werebut it appears i am wrong.
may i ask the core devs: why?
derek
Yuri Baburov wrote:
> 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 postgre
On 10/23/07, Derek Anderson <[EMAIL PROTECTED]> wrote:
> are column defaults not supposed to be set by django under postgres?
Django doesn't set defaults in the database at all.
The basic reason is that too many defaults simply couldn't be
represented in a database -- especially those oriented a
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
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 NU
