| From: | Greg Stark <gsstark(at)mit(dot)edu> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Greg Stark <gsstark(at)mit(dot)edu>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Apparent anomaly with views and unions |
| Date: | 2005-02-13 06:40:33 |
| Message-ID: | 87sm4155em.fsf@stark.xeocode.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:
> I see nothing at all in the spec that justifies the idea of "keep around
> the source text and reinterpret it". They don't think that way; they
> think in terms of thoroughly-processed "descriptors" stored in the
> system catalogs.
Huh. The thing I find most jarring about this way of thinking is that it means
I can have objects in my database that don't correspond to any source code I
have saved.
Say I want to add an expression to a view, I can't safely take the source as I
created it in the past, add the column, and recreate it. The actual view in
the database may no longer correspond to the create statement I have saved.
I suppose you could say that's no different than the create table statements
which could be obsoleted by a series of alter tables.
--
greg
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2005-02-13 06:48:58 | Re: problem with thai language |
| Previous Message | Tom Lane | 2005-02-13 06:25:43 | Re: Apparent anomaly with views and unions |