Re: Trouble with NEW - Mailing list pgsql-general

From Bob Pawley
Subject Re: Trouble with NEW
Date
Msg-id 1378EA3AD30648418F63691CCE37D8B8@BobPC
Whole thread Raw
In response to Re: Trouble with NEW  (Adrian Klaver <adrian.klaver@gmail.com>)
Responses Re: Trouble with NEW  (Adrian Klaver <adrian.klaver@gmail.com>)
Re: Trouble with NEW  (Alban Hertroys <haramrae@gmail.com>)
List pgsql-general
When I substitute new.fluid_id for the actual fluid)id the expression
returns the right value.

Following is the table -

CREATE TABLE p_id.fluids
(
  p_id_id integer,
  fluid_id serial,
  text_arrow geometry,
  line geometry,
  ip_op_equipment character varying(3),
  pipe_number character varying(100),
  pipe_size character varying,
  pipe_size_unit varchar (30),
  pipe_schedule varchar (30),
  dest_process varchar (30),
  dest_pump varchar (30),
  dest_pid varchar (30),
  source_process varchar (30),
  source_pump varchar (30),
  source_pid varchar (30),
  fluid_short character varying (10),
  fluid_name character varying(100),
  pump1 character varying(5),
  pump2 character varying(5),

  CONSTRAINT fluid_pk PRIMARY KEY (fluid_id)
);

Bob
-----Original Message-----
From: Adrian Klaver
Sent: Wednesday, July 18, 2012 1:07 PM
To: Bob Pawley
Cc: Alan Hodgson ; pgsql-general@postgresql.org
Subject: Re: [GENERAL] Trouble with NEW

On 07/18/2012 12:28 PM, Bob Pawley wrote:
> It's an insert after trigger function.
>
> The table has a column named fluid_id.

Can we see the table schema. What I am looking for is quoted column name
that would preserve case.

>
> Bob



--
Adrian Klaver
adrian.klaver@gmail.com


pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: problem with dblink and "drop owned by"
Next
From: Tatsuo Ishii
Date:
Subject: Re: [BUGS] main log encoding problem