Forum OpenACS Development: Re: HEADache ...

Collapse
3: Re: HEADache ... (response to 1)
Posted by Don Baccus on 02/16/03 04:11 AM
It looks like it is coughing on the redefinition of the function fired by the trigger.  Both definitions will have type opaque so that makes me wonder if it is a PG bug.  Peter, I'll be interested to see what you find out.

BTW HEAD is slightly whacked out at the moment.  I've concentrated on getting my permissions changes into 4.6.1 - originally they were going into 4.7 but after 4.6 proved to be absolutely unscalable in the face of lots of groups and relational segments (i.e. "dotLRN") got moved to 4.6.1.

I'll be cleaning up HEAD tomorrow or Monday AM ...

Collapse
4: Re: HEADache ... (response to 3)
Posted by Matthew Walker on 02/16/03 04:37 AM
In PG 7.3 they have redefined the return type for trigger functions from 'OPAQUE' to 'TRIGGER'. They do this automagically for new functions but it seems that when 'create or replace function' is used in 7.3 with a return type of opaque it doesn't like it because it thinks you are trying to redefine the return type of the existing function (which it automagically changed from opaque to trigger).

The solution for 7.3 currently is to change the return type to trigger for the two trigger functions (membership_rels_in_tr and composition_rels_in_tr) that are replaced in acs-kernel/sql/postgresql/groups-body-create.sql (these are originally created in acs-kernel/sql/postgresql/groups-create.sql as placeholders). The problem is this then won't work in PG 7.1 or 7.2.

Matthew