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

Peripheral Links

Header And Logo

PostgreSQL
| The world's most advanced open source database.

Site Navigation

Search for
  Advanced Search

Re: Version 8.1



Thanks Jeff

I'm going through a learning curve. I don't need to add possible instability.

Thanks again.

Bob
----- Original Message ----- From: "Jeff Davis" <pgsql(at)j-davis(dot)com>
To: "Bob Pawley" <rjpawley(at)shaw(dot)ca>
Cc: "Postgresql" <pgsql-general(at)postgresql(dot)org>
Sent: Wednesday, November 29, 2006 4:41 PM
Subject: Re: [GENERAL] Version 8.1


On Wed, 2006-11-29 at 15:31 -0800, Bob Pawley wrote:
I may as well bite the bullet.


If you're going to migrate to 8.1, you might consider migrating to 8.2
since it's almost released. That depends on your timeline though; 8.1 is
a safer bet if you need stability now.

Is this the syntax to use ???

 CREATE OR REPLACE FUNCTION p_id.loopnumber()
 RETURNS "trigger" AS $$

 Update p_id.loop_sequence
 Set function_ = library.devices.designation
 From p_id.loops
 where p_id.loop_sequence.monitor = p_id.devices.devices_id
 and p_id.devices.device_number = library.devices.device_number ;

  RETURN NULL;
 END;
 $$
 LANGUAGE 'plpgsql' ;

 CREATE TRIGGER loopnumbering AFTER INSERT ON p_id.loops
 FOR EACH ROW EXECUTE PROCEDURE p_id.loopnumber();


I think you need library.devices and p_id.devices in the fromlist. Also,
why is p_id.loops in the fromlist if it's not a part of the WHERE?

Regards,
Jeff Davis


---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?

http://www.postgresql.org/docs/faq




Home | Main Index | Thread Index

Privacy Policy | PostgreSQL Archives hosted by Command Prompt, Inc. | Designed by tinysofa
Copyright © 1996 – 2008 PostgreSQL Global Development Group