Received: from orion.SAPserv.Hamburg.dsh.de (Tpolaris2.sapham.debis.de [53.2.131.8]) by hub.org (8.9.1/8.9.1) with SMTP id GAA29736 for ; Thu, 5 Nov 1998 06:47:20 -0500 (EST) (envelope-from wieck@sapserv.debis.de) Received: by orion.SAPserv.Hamburg.dsh.de for pgsql-sql@postgreSQL.org id m0zbODB-000EBYC; Thu, 5 Nov 98 13:08 MET Message-Id: From: jwieck@debis.com (Jan Wieck) Subject: Re: Rules (was: Re: [SQL] How can I optimize...) To: elangog@wipinfo.soft.net (G.Elangovan) Date: Thu, 5 Nov 1998 13:08:25 +0100 (MET) Cc: jwieck@debis.com, mwm@phone.net, pgsql-sql@postgreSQL.org Reply-To: jwieck@debis.com (Jan Wieck) In-Reply-To: from "G.Elangovan" at Nov 5, 98 10:36:37 am X-Mailer: ELM [version 2.4 PL25] Content-Type: text > > I tried Creating RULE with both the example > In first example both the rule failed with error "old table not found" > In case of second example > i managed to create > > [...] > > ERROR: old: Table does not exist. > Please giveme some more info on the KEY word (NEW and OLD).attribute > Note : iam using postgresql 6.3.2 > > Thanku , for ur kind help DON'T TRY TO USE THE RULE SYSTEM IN A v6.3.2 DATABASE. IT'S BUGGY AND DOES NOT WORK AT ALL. All I wrote depends on the major changes I've done in the rule system for v6.4. In v6.4 CURRENT is aliased with OLD and in v6.5 CURRENT will disappear completely. Jan -- #======================================================================# # It's easier to get forgiveness for being wrong than for being right. # # Let's break this rule - forgive me. # #======================================== jwieck@debis.com (Jan Wieck) #