| From: | "Josh Berkus" <josh(at)agliodbs(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Josh Berkus <josh(at)agliodbs(dot)com> |
| Cc: | Richard Ray <rray1(at)netdoor(dot)com>, pgsql-novice(at)postgresql(dot)org |
| Subject: | Re: What causes a table's oid to change? |
| Date: | 2002-10-09 05:27:20 |
| Message-ID: | web-1776617@davinci.ethosmedia.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-novice |
Tom,
> 7.3 fixes it, if you consider a fix to be disallowing drop of a table
> that has dependent views...
>
> regression=# create table t1 (f1 int);
> CREATE TABLE
> regression=# create view v1 as select * from t1;
> CREATE VIEW
> regression=# drop table t1;
> NOTICE: rule _RETURN on view v1 depends on table t1
> NOTICE: view v1 depends on rule _RETURN on view v1
Cool! This wouldn't be much of a fix if you hadn't implemented DROP
COLUMN as well, but with that, it helps a lot.
One of the most gratifying things about being part of the Postgresql
commmunity is being able to see the (rapid) progress happen.
-Josh
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sudheesh Krishnankutty | 2002-10-09 05:30:01 | How to store encrypted data into database |
| Previous Message | Tom Lane | 2002-10-09 05:10:52 | Re: What causes a table's oid to change? |