| From: | "Ed L(dot)" <pgsql(at)bluepolka(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: plpgsql/rule question |
| Date: | 2005-01-12 04:02:29 |
| Message-ID: | 200501112102.29684.pgsql@bluepolka.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Tuesday January 11 2005 8:58, Tom Lane wrote:
> "Ed L." <pgsql(at)bluepolka(dot)net> writes:
> > The reason I ask is because I'd like to allow any explicitly specified
> > values for the view insert, including NULL, to be passed through to the
> > table insert and override the column defaults.
>
> Possibly you can solve your problem by attaching the defaults to the
> view, not to the table at all. ALTER TABLE view ALTER COLUMN col SET
> DEFAULT something has worked for a number of PG releases...
Perfect, thanks. The more I learn, the less I know.
Ed
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Stark | 2005-01-12 04:57:42 | Re: Bug in pg_dump in 7.4.6? |
| Previous Message | Michael Fuhr | 2005-01-12 04:02:23 | Re: plpgsql/rule question |