| From: | PFC <lists(at)boutiquenumerique(dot)com> |
|---|---|
| To: | "Kenneth Gonsalves" <lawgon(at)thenilgiris(dot)com>, weberp(at)paradise(dot)net(dot)nz |
| Cc: | pgsql-sql(at)postgresql(dot)org |
| Subject: | Re: Query performance problem |
| Date: | 2005-03-17 13:57:40 |
| Message-ID: | opsnsbqe05th1vuj@localhost |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-sql |
> although may be not relevant to your question, as i have noticed this
> before with mysql 'sql', what is the point of having a NOT NULL field
> that defaults to 0? the whole idea of a NOT NULL field is to have the
> value filled in compulsorily and having a default of 0 or '' defeats
> the purpose
Well if you define your field as NOT NULL mysql will automatically set it
to 0 if you store a NULL anyway, so you might as well specify it in your
table definitions so it looks like you wanted it...
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephan Szabo | 2005-03-17 14:01:27 | Re: update with subselect (long) |
| Previous Message | Leif B. Kristensen | 2005-03-17 13:36:51 | Re: update with subselect (long) |