From: jwieck@debis.com
To: hannu@trust.ee
Cc: jwieck@debis.com
Cc: pgsql-hackers@postgreSQL.org
Cc: maillist@remo.demon.co.uk
Cc: pgsql-sql@postgreSQL.org
Subject: Re: [HACKERS] RULE (and ALTER TABLE) questions
Date: Fri, 12 Feb 1999 20:16:57 +0100 (MET)
Message-ID: <m10BO5B-000EBRC@orion.SAPserv.Hamburg.dsh.de> (raw)
In-Reply-To: <36C46055.50875098@trust.ee>
> 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) #
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-sql@postgresql.org
Cc: jwieck@debis.com, hannu@trust.ee, pgsql-hackers@postgreSQL.org, maillist@remo.demon.co.uk
Subject: Re: [HACKERS] RULE (and ALTER TABLE) questions
In-Reply-To: <m10BO5B-000EBRC@orion.SAPserv.Hamburg.dsh.de>
References: <36C46055.50875098@trust.ee> <m10BO5B-000EBRC@orion.SAPserv.Hamburg.dsh.de>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox