I'm using PostgreSQL 7.3.4.
I've set up a series of rules and triggers to complete an intermediate
table with similar informations from another table. This ensures better
performance over a solution with views.
Intermediate table:
Table album_edit
Field Type Length Not NullDe
This is a resent. Wrong email account the first time.
---
I'm using PostgreSQL 7.3.4.
I've set up a series of rules and triggers to complete an intermediate
table with similar informations from another table. This ensures better
performance over a solution with views.
Intermediate table:
Tab
At 21:28 31/07/2004 -0400, Tom Lane wrote:
>>> Now my questions are:
>>> - Is this an expected behavior ?
> It is. Rules are essentially macros and so you have all the usual
> potential gotchas with multiple evaluations of their input arguments.
I've understood what was done by the evaluation proc
Forgive me if this is not a bug. But I have a problem with a rule on a
table which has a column with a sequence.
I'm using postgres 7.3.4.
I have a table named "album" with the following structure (part only)
CREATE TABLE album (
id integer DEFAULT nextval('"album_id_seq"'::text) NOT NULL,