Postgres PL SQL bug?
Hi All
Im hoping someone has an answer for this mystery.
I have a stored procedure, which queries a table, of about 400-000 records,
into a RECORD, ordered by three columns.
I am using a conditional INSERT, UPDATE command, based on evaluating the
last record.column, against the new record.column, to ascertain whether it
requires, an UPDATE or INSERT.
The problem is the records are not ORDERED properly into the RECORD, and
when looping through it,it is trying to INSERT somewhere down the line, and
is returning an error, saying it cant INSERT a duplicate key into unique..
etc.
Any suggestions, the postgres version is 7.3
Thanks in advance.
Kind Regards,
Shaun Clements
Shaun Clements wrote:
The problem is the records are not ORDERED properly into the RECORD, and
when looping through it,it is trying to INSERT somewhere down the line, and
is returning an error, saying it cant INSERT a duplicate key into unique..
etc.
What do you mean by not ordered properly? How have you tried to order
them and how have they actually been ordered?
--
Richard Huxton
Archonet Ltd