| From: | "Eric G(dot) Miller" <egm2(at)jps(dot)net> |
|---|---|
| To: | Lista PostgreSql <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Inheritance and views |
| Date: | 2001-04-05 01:16:14 |
| Message-ID: | 20010404181614.A23460@calico.local |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Wed, Apr 04, 2001 at 02:07:13PM +0200, DaVinci wrote:
> Hello.
>
> I'd like to implement for my DB a mechanism of backup based in inherited
> tables. I explain it in detail:
>
> Idea is simple: table B inherits from table A. Anualy, data from table A is
> dumped in B. So, from frontend it is posible to access current data (from
> A) or all data (A + B).
>
> Problem is that I'd like also implement a view for A and B, but I don't
> know what is best way. View(s) must have rules for insert and update. Can
> view from A access data from B without problem (eliminating "ONLY" from
> select)?. Is there another better form of implementing this backup
> mechanism?. I'd not want to reinvent the wheel ;)
>
> Thanks for your ideas.
Maybe...
SELECT * FROM A* ;
Notice the asterisk on the superclass table name.
--
Eric G. Miller <egm2(at)jps(dot)net>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Norman J. Clarke | 2001-04-05 01:35:26 | RE: JBuilder4 JDBC Explorer |
| Previous Message | Norman J. Clarke | 2001-04-05 01:13:29 | Re: JBuilder4 JDBC Explorer |