On Tue, 12 Nov 2002, Bob Kimble wrote:
> Well, I think that PostgreSQL is behaving exactly as expected by an RDBMS
> performing a transaction.
Uh, I don't think so. The database should never rollback a transaction
unless I tell it to. It's responsibility is to tell me of the
error. What happens after that is up to me. Oracle does this, and I'm
pretty sure DB2 and Sybase do as well.
> Perhaps you could use a rule to achieve what you want. You could create a
> clone of table 2 augmented with a rule that checks to see if the row you just
> inserted into the clone exists already in table 2. If so, it just drops the
Ah, I'll just do a SELECT to see if the row already exists, and if it
does, skip the insert. It's easier. It's just that, I shouldn't have
to. . .
Cheers,
Bob
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
lmpx.com only provides a reader for public news (NNTP) servers. It is not
affiliated with the servers or forums shown here and is not responsible for
the content of articles, which is written by their respective authors.