Home > mailing lists

Thread: Postgres PL SQL bug?

Postgres PL SQL bug?

From

Shaun Clements

Date:

31 March 2005, 18:32:49

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.

A {FONT-FAMILY: verdana; TEXT-DECORATION: none } A:active {COLOR: #ff0000; FONT-FAMILY: verdana; TEXT-DECORATION: none } A:link {COLOR: #003366; FONT-FAMILY: verdana; TEXT-DECORATION: none } A:visited {COLOR: #003366; FONT-FAMILY: verdana; TEXT-DECORATION: none } A:hover {COLOR: #ff0000; FONT-FAMILY: verdana; TEXT-DECORATION: underline } .small_text {FONT-SIZE: 9px; COLOR: #003366; FONT-FAMILY: verdana } Kind Regards,
Shaun Clements

Re: Postgres PL SQL bug?

From

Richard Huxton

Date:

31 March 2005, 20:03:06

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