Gary Stainburn wrote:
I found that the compile error complaining about the 'OR' was on theCREATE OR REPLACE FUNCTION line. I removed the 'OR REPLACE' and everything worked fine.
OR REPLACE is since postgres 7.2
In this case it's ok to "return null", but if you create "before" trigger you shoud "return new", because "return null" forces postgres not to insert any data.
Also I had to change the returns to 'opaque' and 'return 0' to 'return null'
Tomasz Myrta
---------------------------(end of broadcast)---------------------------
TIP 4: Don't 'kill -9' the postmaster