I apologize for not expressing myself clearly, and for replying without really giving any new information. In hindsight
Iunderstand perfectly well, why you did not want to continue communication, but I hope that you or someone else, will
giveme a second chance on the issue.
Let me try to explain what I really meant:
Let's say you are trying to make a generic database maintenance system. One of the tasks of this system is to update
individualrows. For various reasons you may want to deal with views and not only tables. You may also want these views
tobe updated on and inserted on. I completely agree with you that using OID as a primary key as in PRIMARY KEY(oid),
andthen REFERENCES etc, or generally storing the oid anywhere in tables. However if you are simply trying to update it
isvery usefull - especially with views as you have no way of determining what the primary key of the table is!
Therefore I would suggest that one could assign the field oid in a view, (but that it still remains hidden from *) such
thatthese kinds of issues are simpler. I have solved the problem in my case otherwise, and I totally agree that it is
notimportant - it's just very usefull, in this and a few other cases.
Regards,
Aasmund.
On Sat, 20 Oct 2001 12:58:09 -0700, "Josh Berkus" <josh@agliodbs.com> wrote:
> Aasmund,
>
>
> This is my last e-mail, as you are not listening to my advice.
>
> *Do NOT use OIDs as your primary key for any table!* If you persist in
> doing so, the problems you encounter are your own fault, and you will
> get no help with them from the list or the developers.
>
> -Josh
>
> ______AGLIO DATABASE SOLUTIONS___________________________
> Josh Berkus
> Complete information technology josh@agliodbs.com
> and data management solutions (415) 565-7293
> for law firms, small businesses fax 621-2533
> and non-profit organizations. San Francisco
>
>
>
Aasmund Midttun Godal
aasmund@godal.com - http://www.godal.com/
+47 40 45 20 46
