Thread: What's ETA for read/write Views?

I'm working on a project and using postgres 7.0.2
with phpPgAdmin and php3.0.16.  Anyhow, the more
I learn about relations database systems, the more
orthogonal my data becomes.  However, I then need
to have read/write views so that "ordinary" humans
can make sense of the data....   While, I'm at it. I've always disliked MySQL
because it wasn't GPL'd nor was it a real RDBMS.
Anyhow, from what I can tell, they went GPL because
that was the only way to move forward due to their
BDB kludge.....Just my 2 cents....

TIA.
tim
dirac@applink.net

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

Tom Lane writes:

> 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?

The SQL standard has pretty precise rules for when views are updatable and
how.


-- 
Peter Eisentraut                  Sernanders väg 10:115
peter_e@gmx.net                   75262 Uppsala
http://yi.org/peter-e/            Sweden