Forum OpenACS Development: acs_data_links error when upgrading acs-kernel

Hi Ryan,

I got the following error when upgrading acs-kernel:

Error: apm_package_install: Error installing Kernel version 5.6.0d4: psql:upgrade-5.6.0d3-5.6.0d4.sql:3: ERROR: cannot drop index acs_data_links_un because constraint acs_data_links_un on table acs_data_links requires it
HINT: You may drop constraint acs_data_links_un on table acs_data_links instead.
psql:upgrade-5.6.0d3-5.6.0d4.sql:7: ERROR: relation "acs_data_links_un" already exists

psql:upgrade-5.6.0d3-5.6.0d4.sql:3: ERROR: cannot drop index acs_data_links_un because constraint acs_data_links_un on table acs_data_links requires it
HINT: You may drop constraint acs_data_links_un on table acs_data_links instead.
psql:upgrade-5.6.0d3-5.6.0d4.sql:7: ERROR: relation "acs_data_links_un" already exists

invoked from within
"db_source_sql_file -callback $callback $path/$file_path"
(procedure "apm_package_install_data_model" line 32)
invoked from within
"apm_package_install_data_model -callback $callback -data_model_files $data_model_files $spec_file_path"
invoked from within
"if { $load_data_model_p } {
apm_package_install_data_model -callback $callback -data_model_files $data_model_files $spec_file_path
..."
("uplevel" body line 55)
invoked from within
"uplevel $body "

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).

Hi Don - I updated the SQL scripts on HEAD to use UNIQUE constraints.