Skip site navigation (1) Skip section navigation (2)

Re: Changes to functions and triggers

From: darcy(at)druid(dot)net (D'Arcy J(dot)M(dot) Cain)
To: Thomas Lockhart <lockhart(at)alumni(dot)caltech(dot)edu>
Cc: hackers(at)PostgreSQL(dot)org
Subject: Re: Changes to functions and triggers
Date: 2000-06-16 22:28:20
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
Thus spake Thomas Lockhart
> > This no longer works.  I looked and the docs and it seems that this
> > should work instead.
> > 
> > CREATE FUNCTION make_date(date, int, int, int)
> >     RETURNS opaque
> >     AS '/usr/pgsql/modules/'
> >     LANGUAGE 'c';
> > CREATE TRIGGER make_edate
> >     FOR EACH ROW
> >     EXECUTE PROCEDURE make_date('edate', 'aniv', 'emon', 'eyear');
> What if you leave out the quotes on the last line above, so the column
> names are actually visible? It looks like the example in the docs might
> be a poor choice since the function is intended to manipulate columns,
> so the text representation of the column name is being passed in.
> Don't know if that is the source of your trouble though...

Nope.  I added that after reading the web page but without them it still
has the problem.

D'Arcy J.M. Cain <darcy(at){druid|vex}.net>   |  Democracy is three wolves                |  and a sheep voting on
+1 416 425 1212     (DoD#0082)    (eNTP)   |  what's for dinner.

In response to

pgsql-hackers by date

Next:From: Tom LaneDate: 2000-06-16 22:48:28
Subject: Re: planner question re index vs seqscan
Previous:From: Pierre-Louis MalatrayDate: 2000-06-16 21:40:02
Subject: ODBC driver problem ??

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group