Tom Lane <[EMAIL PROTECTED]> writes: > Eric D Nielsen <[EMAIL PROTECTED]> writes: > > In either case is this a place where "exceeding" the spec would be a good > > thing or a bad thing? > > Unless there is an obvious definition of what updating a join means > (obvious not only to the implementor, but to the user) I think this > is dangerous territory.
Joins are a *BIG* part of the reason people want updateable views. In every single case that I updated a view it was a join. Just being able to update subsets of tables or restricted sets of columns is really a fairly trivial use of a powerful feature. In Oracle the constraint is fairly straightforward (at least to describe): for each column you're updating the primary key of the table it came from has to be present in the view. -- greg ---------------------------(end of broadcast)--------------------------- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/users-lounge/docs/faq.html
