From: | "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com> |
---|---|
To: | "Marc G(dot) Fournier" <scrappy(at)postgresql(dot)org>, David Fetter <david(at)fetter(dot)org>, Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-advocacy(at)postgresql(dot)org, Simon Riggs <simon(at)2ndquadrant(dot)com> |
Subject: | Re: Feedback from LinuxWorld, London |
Date: | 2005-10-11 00:18:01 |
Message-ID: | 20051011001801.GK39569@pervasive.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-advocacy |
On Mon, Oct 10, 2005 at 05:05:46PM -0700, elein wrote:
> On Mon, Oct 10, 2005 at 05:42:31PM -0300, Marc G. Fournier wrote:
> > On Mon, 10 Oct 2005, David Fetter wrote:
> >
> > >In this case, it might be easier to make a writeable VIEW with two
> > >tables underneath and an appropriate call to ARRAY() and maybe to
> > >array_to_string()
> >
> > Is there any work being done on UPDATEABLE VIEWs? I found, at one point,
> > a 'work around' for it, but just wondering if there is any work being done
> > on a more 'native' method ...
>
> We have updateable views if you write the rules for them.
> A default updateable view could only be accurate all the
> time if it only contained a single table reference. Our
Well, you can create multi-table views that are also updateable. IIRC
the restriction is that joins must all be inner joins and you can't be
doing any kind of group by. I know the DB2 docs talk about this and I'm
pretty sure Oracle's do as well.
--
Jim C. Nasby, Sr. Engineering Consultant jnasby(at)pervasive(dot)com
Pervasive Software http://pervasive.com work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461
From | Date | Subject | |
---|---|---|---|
Next Message | elein | 2005-10-11 00:55:45 | Re: Feedback from LinuxWorld, London |
Previous Message | elein | 2005-10-11 00:05:46 | Re: Feedback from LinuxWorld, London |