Hi Jasen.
Thank you for your response (also thank you to Tom).
I have now tried your suggestion, but I'm not sure how you have implemented
the plpgsql function. When I create the function: CREATE update_rule_func( old
record, new record ) AS ... I am told, that I cannot use record
Hi Leif,
Am 22.01.2013 14:34, schrieb Leif Jensen:
CREATE update_rule_func( old record, new record ) AS ... I am told, that I
cannot use record for the parameter type. Could you please
You should use your view instead of 'record' as parameter type, i.e. CREATE
update_rule_func( old
Hi Marc,
Thanks a lot. That works fine. The names 'NEW' and 'OLD' works fine.
Leif
- Marc Schablewski m...@clickware.de wrote:
Hi Leif,
Am 22.01.2013 14:34, schrieb Leif Jensen:
CREATE update_rule_func( old record, new record ) AS ... I am told,
that I cannot use record
Hello,
I have been fighting a problem with an update rule on a view. I have a view
that combines two tables where the 'sub' table (scont) can have several rows
per row in the 'top' table (icont). The view combines these to show only one
record per row in the top table. To be able to
Leif Jensen l...@crysberg.dk writes:
I have been fighting a problem with an update rule on a view. I have a
view that combines two tables where the 'sub' table (scont) can have several
rows per row in the 'top' table (icont). The view combines these to show only
one record per row in the
On 2013-01-18, Leif Jensen l...@crysberg.dk wrote:
I have been fighting a problem with an update rule on a view. I
have a view that combines two tables where the 'sub' table (scont) can
have several rows per row in the 'top' table (icont). The view
combines these to show only one record
