| From: | Christopher Kings-Lynne <chris(dot)kings-lynne(at)calorieking(dot)com> |
|---|---|
| To: | Greg Stark <gsstark(at)mit(dot)edu> |
| Cc: | Hannu Krosing <hannu(at)skype(dot)net>, Zeugswetter Andreas DCP SD <ZeugswetterA(at)spardat(dot)at>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: ADD/DROP INHERITS |
| Date: | 2006-06-09 01:17:27 |
| Message-ID: | 4488CC27.8030707@calorieking.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> I forget whether the developer managed to get it working without doing any
> table rewriting. In theory the table just needs to know that records that are
> "missing" that column in the null bitmap should behave as if they have the
> default value. But I seem to recall some headaches with that approach.
The problem is if you then change the default.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Fetter | 2006-06-09 01:32:17 | Re: Fabian Pascal and RDBMS deficiencies in fully implementing the relational model |
| Previous Message | Trent Shipley | 2006-06-09 01:09:21 | Re: Fabian Pascal and RDBMS deficiencies in fully implementing the relational model |