Hi, Daniel,
Daniel Drotos wrote:
>> What is it that you're trying to achieve with the ordered delete? Maybe
>> there's a better way to solve your underlying problem.
>
> I've a table which has a field for some info (number) and a date field
> (insertion date) and others.
>
> After inserting new rows into this table, very old rows are going to be
> deleted. But value of deleted info should be remembered somehow, so
> there is a trigger on delete which keeps sum of the deleted info values
> in a separate table. This makes the application happy.
>
> Trigger's algorithm is a little bit more dificult which I would be able
> to simplify if rows are deleted in date order.
Ah, I see.
I don't know exactly what you're doing here, but at least for a sum, the
order of summed values is not relevant.
And due to the transaction system, other applications won't see
inconsistent intermediate states, as the whole DELETE run and all
trigger calls are part of the same transaction.
> Now I'm doing it in a plpgsql function using a `for in select loop' to
> delete rows one by one.
I'm afraid that this is the only solution if you can't simplify the
trigger by other means.
HTH,
Markus
--
Markus Schaber | Logical Tracking&Tracing International AG
Dipl. Inf. | Software Development GIS
Fight against software patents in Europe! www.ffii.org
www.nosoftwarepatents.org