Received: from sss2.sss.pgh.pa.us (sss.pgh.pa.us [209.114.166.2]) by hub.org (8.10.1/8.10.1) with ESMTP id e711XwB24709 for ; Mon, 31 Jul 2000 21:34:06 -0400 (EDT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss2.sss.pgh.pa.us (8.9.3/8.9.3) with ESMTP id VAA19848; Mon, 31 Jul 2000 21:33:41 -0400 (EDT) To: Timothy Covell cc: pgsql-sql@postgresql.org Subject: Re: What's ETA for read/write Views? In-reply-to: <00036dbe0ee2e93c_mailit@smtp.applink.net> References: <00036dbe0ee2e93c_mailit@smtp.applink.net> Comments: In-reply-to Timothy Covell message dated "Mon, 31 Jul 2000 18:59:51 -0500" Date: Mon, 31 Jul 2000 21:33:40 -0400 Message-ID: <19845.965093620@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200007/292 Read-write views exist now: you just have to write ON INSERT, ON UPDATE, ON DELETE rules that show what you think should happen. Some people seem to think that the system should try to intuit those rules for them, but I don't believe that's either possible or desirable. The entire point of a view is that it's not an exact image of the underlying data, so how is a machine going to figure out what you want an update on the view to do? regards, tom lane