Forum OpenACS Development: Re: acs_data_links error when upgrading acs-kernel

Collapse
3: Re: acs_data_links error when upgrading acs-kernel (response to 2)
Posted by Don Baccus on 01/05/10 11:14 PM
Ryan - you should continue to use a UNIQUE table constraint for the three columns rather than manually generate the index. That's the standard SQL way to do it and works equivalently in Oracle and PG.

(as it happens both implement UNIQUE constraints by building the multi-column index but please, stick to standard SQL when possible).

Collapse
4: Re: acs_data_links error when upgrading acs-kernel (response to 3)
Posted by Ryan Gallimore on 01/06/10 10:14 AM
Hi Don,

I realize that a unique constraint is the standard, however this Oracle post seems to prove that a unique index is not always created when a unique constraint is created. It recommends creating a unique index explicitly.

If that was the correct method for Oracle, I wanted to be consistent in PG and use a unique index as well.

With the Oracle quirk in mind, how should I change my script?

Collapse
5: Re: acs_data_links error when upgrading acs-kernel (response to 3)
Posted by Ryan Gallimore on 01/06/10 09:09 PM
Hi Don - I updated the SQL scripts on HEAD to use UNIQUE constraints.