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
technique is more flexible and powerful, but scarier due
to RULES being scary. There are documents on this, however,
and the rules are quite simple if the developer knows what
they want done when the view is updated.
--elein
>
> >>That was actually the context of the enum discussion. I threw enum
> >>out as an example and everyone latched onto it, missing the overall
> >>point of trying to improve migration from MySQL.
> >
> >I didn't :)
>
> I did, only as an example ... the question, on my part, being how many
> things could we 'mask', not so much focusing on enum itself :)
>
> ----
> Marc G. Fournier Hub.Org Networking Services (http://www.hub.org)
> Email: scrappy@hub.org Yahoo!: yscrappy ICQ: 7615664
>
> ---------------------------(end of broadcast)---------------------------
> TIP 1: if posting/reading through Usenet, please send an appropriate
> subscribe-nomail command to majordomo@postgresql.org so that your
> message can get through to the mailing list cleanly
>
