From: | Julie Bernhardt <Julie(at)telecomadvocates(dot)com> |
---|---|
To: | "Albin, Lloyd P" <lalbin(at)scharp(dot)org>, "seapug(at)postgresql(dot)org" <seapug(at)postgresql(dot)org> |
Subject: | Re: Trigger Functions |
Date: | 2013-02-15 19:06:41 |
Message-ID: | C3D283C7562A2D439125D7787AD219A32B8458521B@P3PW5EX1MB10.EX1.SECURESERVER.NET |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | seapug |
This would be a good talk. I have to do the upgrade to 9.2. Thank you.
From: seapug-owner(at)postgresql(dot)org [mailto:seapug-owner(at)postgresql(dot)org] On Behalf Of Albin, Lloyd P
Sent: Wednesday, February 13, 2013 3:56 PM
To: seapug(at)postgresql(dot)org
Subject: Re: [seapug] Trigger Functions
Julie,
Question 1: Did I miss / overlook the use of a switch/setting?
This all looks good to me. I created a table and tested everything.
Question 2: Is there an optimal place to put standard functions that many databases will call?
Some people use the public schema, so that you don't have to prepend a schema name, just like with the built in command. We prefer to create a tools schema that we have two sql scripts, one to install and one to update. If you did not want to prepend with the tools schema, you could set the search path to include the tools schema, although we don't do this.
Once we upgrade to Postgres 9.2, we will make the tools schema an extension. Extensions also support upgrade scripts. See:
http://www.postgresql.org/docs/9.2/static/extend-extensions.html
Especially section 35.15.5 for an example of writing an SQL-only extension.
Having never a basic SQL extension, this would make an interesting talk sometime.
Lloyd
From | Date | Subject | |
---|---|---|---|
Next Message | Lee Fisher | 2013-02-16 00:40:34 | Fwd: [SEAPY] no February meeting scheduled |
Previous Message | Lee Fisher | 2013-02-15 18:47:31 | Postgres talk at Seattle-Hadoop-HBase-NoSQL-Meetup? |