On Wed, Oct 11, 2006 at 21:31:37 +0200,
Daniel Drotos <[EMAIL PROTECTED]> wrote:
> On Wed, 11 Oct 2006, Markus Schaber wrote:
>
> 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 o
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
On Wed, 11 Oct 2006, Markus Schaber 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 r
Hi, Daniel,
Daniel Drotos wrote:
> What is the best way to do something like:
>
> delete from tablename where something order by somefield...
There should be no need for this, because a delete is atomic due to the
transaction system.
What is it that you're trying to achieve with the ordered d
At 04:14 PM 10/9/06, Daniel Drotos wrote:
What is the best way to do something like:
delete from tablename where something order by somefield...
You cannot, because it doesn't make sense. The "order by" clause is not
valid on delete statement. Queries from other processes that start while
Hi,
What is the best way to do something like:
delete from tablename where something order by somefield...
Daniel
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
