Received: from orion.SAPserv.Hamburg.dsh.de (Tpolaris2.sapham.debis.de [53.2.131.8]) by hub.org (8.9.2/8.9.1) with SMTP id OAA16003; Fri, 12 Feb 1999 14:10:47 -0500 (EST) (envelope-from wieck@sapserv.debis.de) Received: by orion.SAPserv.Hamburg.dsh.de for pgsql-sql@postgreSQL.org id m10BO5B-000EBRC; Fri, 12 Feb 99 20:16 MET Message-Id: From: jwieck@debis.com (Jan Wieck) Subject: Re: [HACKERS] RULE (and ALTER TABLE) questions To: hannu@trust.ee (Hannu Krosing) Date: Fri, 12 Feb 1999 20:16:57 +0100 (MET) Cc: jwieck@debis.com, pgsql-hackers@postgreSQL.org, maillist@remo.demon.co.uk, pgsql-sql@postgreSQL.org Reply-To: jwieck@debis.com (Jan Wieck) In-Reply-To: <36C46055.50875098@trust.ee> from "Hannu Krosing" at Feb 12, 99 07:09:41 pm X-Mailer: ELM [version 2.4 PL25] Content-Type: text > But when doing that at the table creation time, then the table can > actually > be defined as a view on storage table and rules for insert update and > delete > be defined for this view that do the actual data manipulation on the > storage table. That's IMHO a too specific case to do it generally with the rule system. Should be some kind of constraint handled by the parser in putting an UPPER() func node around the targetlist expression. There could be more general support implemented, in that a user can allways tell that a custom function should be called with the result of the TLE-expr before the value is dropped into the tuple on INSERT/UPDATE. 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) #