Tom Lane wrote:
>
> Well, if that's how your application logic works then you're done.
Great! It's not _my_ application logic, someone else's. I'm trying to
find a way to make it more postgres friendly and generate less error
messages.
The application was first written for MySQL and the business _logic_
seems to have been to just throw inserts at the database and if they
failed it must be because the record was already there so no need to
worry about it.
Pretty loose logic but then again the app can be *very* write intensive
and the extra cycles needed to check whether something is already in
the DB or not before inserting seems to be a real concern for the
application developers.
Jean-Christian Imbeault