Re: error when creating rule - Mailing list pgsql-general

From Stephan Szabo
Subject Re: error when creating rule
Date
Msg-id 20031107073521.V82577@megazone.bigpanda.com
Whole thread Raw
In response to error when creating rule  (Barbara Lindsey <blindsey@cog.ufl.edu>)
Responses Re: error when creating rule
List pgsql-general
On Fri, 7 Nov 2003, Barbara Lindsey wrote:

> CREATE SEQUENCE "prod_id_seq" cache 1;
> CREATE TABLE "prod_data" (
>         "prod_id" integer DEFAULT nextval('prod_id_seq') PRIMARY KEY,
>         "client_id" integer NOT NULL,
>         "cat_id" integer NOT NULL,
>         "status_id" integer NOT NULL,
>         "modified" timestamp with time zone DEFAULT  current_timestamp,
>         "modified_by" varchar(50) DEFAULT current_user,
>         CONSTRAINT prod_clnt_fk FOREIGN KEY (client_id)
>            REFERENCES ref_clients(client_id)
>            ON DELETE CASCADE ON UPDATE CASCADE,
>         CONSTRAINT prod_cat_fk FOREIGN KEY (cat_id)
>            REFERENCES ref_category(cat_id)
>            ON DELETE CASCADE ON UPDATE CASCADE,
>         CONSTRAINT prod_stat_fk FOREIGN KEY (status_id)
>            REFERENCES ref_status(status_id)
>            ON DELETE CASCADE ON UPDATE CASCADE
> );
>
> TABLE  job_data_bak looks just like job_data but with all constraints
> removed.
>
>
> Here is where the problem begins. When I try to create this rule:
>
> CREATE RULE log_prod_upd AS ON UPDATE TO prod_data
>      where NEW.prod_id = OLD.prod_id
>      DO INSERT INTO job_data_bak VALUES (
>           OLD.prod_id,OLD.client_id,
>           OLD.cat_id, OLD.status_id,
>           OLD.modified,OLD.modified_by
>      );

Was this intended to go to prod_data_bak as opposed to job_data_bak?

pgsql-general by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: int8 primary keys still not using index without manual
Next
From: Barbara Lindsey
Date:
Subject: Re: error when creating rule