Rules & cycles

Is it possible to avoid a rule calling itself, as it were?

i.e.

CREATE TABLE test (testnumber float8,testid serial primary key);

CREATE FUNCTION adjust(float8) RETURNS '
SELECT dpow(1.14,$1) AS result;'
LANGUAGE 'SQL';

CREATE RULE testtest AS ON INSERT TO test
DO INSTEAD INSERT INTO test (testnumber) VALUES
(adjust(new.testnumber));

INSERT INTO test VALUES (2);

now gets into an endless loop, which postgres intelligently breaks out
of with an ERROR:

What I want is just to make that substitution once!

If possible I want to do this without rewriting my application to use
a view of the table rather than the table itself...

Yours,
Moray

----------------------------------------------------------------------
----------------
Moray(dot)McConnachie(at)computing-services(dot)oxford(dot)ac(dot)uk
----- Original Message -----
From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: PostgreSQL-announce <announce(at)postgreSQL(dot)org>; PostgreSQL-general
<pgsql-general(at)postgreSQL(dot)org>
Sent: Thursday, November 18, 1999 12:41 PM
Subject: [GENERAL] Book completed through chapter 6

> I have completed through chapter 6 of my book, "PostgreSQL:
> Introduction and Concepts." Of course, this is only the first
draft.
> It can be viewed at:
>
> http://www.postgresql.org/docs/awbook.html
>
> There are major improvements in this version. I have added sections
to
> chapter 4 dealing with DEFAULT and functions/operators. The figure
> placement and font usage is improved.
>
> Chapter 6 covers using multiple tables and joins. This was a very
> difficult chapter for me to write.
>
> --
> Bruce Momjian | http://www.op.net/~candle
> maillist(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
> + If your life is a hard drive, | 830 Blythe Avenue
> + Christ can be your backup. | Drexel Hill, Pennsylvania
19026
>
> ************
>
>