<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content="text/html; charset=us-ascii" http-equiv=Content-Type>
<META name=GENERATOR content="MSHTML 8.00.6001.18852"></HEAD>
<BODY><FONT color=#0000ff size=2 face=Arial></FONT>
<DIV dir=ltr align=left><SPAN class=465250510-06122009><FONT color=#0000ff
size=2 face=Arial> Ragi, </FONT></SPAN><BR><SPAN
class=465250510-06122009><FONT color=#0000ff size=2 face=Arial> >
</FONT></SPAN>Hello Regina and thank you so much for joining the
conversation. IMHO an application that will not execute edits on an updatable
view is an <SPAN class=465250510-06122009><FONT color=#0000ff size=2
face=Arial> </FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=465250510-06122009><FONT color=#0000ff
size=2 face=Arial>> </FONT></SPAN>application with a bug :) <SPAN
class=465250510-06122009><FONT color=#0000ff size=2
face=Arial> </FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=465250510-06122009><FONT color=#0000ff
size=2 face=Arial></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=465250510-06122009><SPAN
class=465250510-06122009> </SPAN><BR>> However, you do have a valid
point. <BR><BR>> Changing the logic of application to be able to edit rows
that don't have primary keys is probably a crazy request so I will not go there
(I am thinking how all the rows in OGR, for example, require an
ObjectID).</SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=465250510-06122009></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=465250510-06122009><FONT color=#0000ff
size=2 face=Arial>Well its kind of questionable where the bug lies. The
ideal place to fix said bug is in PostgreSQL. If PostgreSQL had some
mechanism in creating a view to denote what the primary key SHOULD
be.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=465250510-06122009></SPAN><SPAN
class=465250510-06122009><FONT color=#0000ff size=2
face=Arial> </FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=465250510-06122009><FONT color=#0000ff
size=2 face=Arial>Or less desirable for the application (such as what
MapServer has -- to allow the user to dictate what the primary key
is)</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=465250510-06122009><FONT color=#0000ff
size=2 face=Arial></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=465250510-06122009><FONT color=#0000ff
size=2 face=Arial> > </FONT></SPAN>Think about the alternative of
*not* using views. I would always have to append _v1 or _v2 or _v3 to my
ALL my tables names to get <SPAN class=465250510-06122009><FONT
color=#0000ff size=2 face=Arial> </FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=465250510-06122009><FONT color=#0000ff
size=2 face=Arial>> </FONT></SPAN>the <SPAN
class=465250510-06122009><FONT color=#0000ff size=2
face=Arial> </FONT></SPAN>right <SPAN class=465250510-06122009><FONT
color=#0000ff size=2 face=Arial> </FONT></SPAN>results. It just
becomes inconvenient for scripts and such. An that is the scenario where we are
talking about workspace-level <SPAN class=465250510-06122009><FONT
color=#0000ff size=2 face=Arial> </FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=465250510-06122009><FONT color=#0000ff
size=2 face=Arial>> </FONT></SPAN>versioning. If we are talking tables,
ugh, I don't even want think about it - it would be horrible.<BR><SPAN
class=465250510-06122009><FONT color=#0000ff size=2 face=Arial> But I agree
with you leveraging views or inherited tables with rules is probably the
best bet. </FONT></SPAN><BR><SPAN class=465250510-06122009><FONT
color=#0000ff size=2 face=Arial> </FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=465250510-06122009><FONT color=#0000ff
size=2 face=Arial>Thanks,</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=465250510-06122009><FONT color=#0000ff
size=2 face=Arial>Regina</FONT> </SPAN></DIV></BODY></HTML>