Ticket #173 (closed defect: fixed)

Opened 7 years ago

Last modified 6 years ago

MUA PostgreSQL Schema Issue

Reported by: https://idp.heanet.ie/idp/shibboleth!https://iam.cf.ac.uk/sp/shibboleth!zvmxrzixwj18dvunhwfpbdpvatk= Owned by: Phil Smart
Priority: minor Milestone: v1.2.1
Component: Raptor MUA Version: v1.1.4
Keywords: Schema Cc:



There seems to be a duplicated INDEX within the MUA PostgreSQL schema, which throws an error when it is imported.

ERROR: relation "hashcode_i" already exists

The hashcode_i index appears to be already defined for the EzproxyAuthenticationEvent? table, and tries to be created again for the ShibbolethIdpAuthenticationEvent? table.

PostgreSQL is version 8.4
MUA version 1.1.4
MUA Schema Version 3




insert_log.txt (1.3 KB) - added by https://idp.heanet.ie/idp/shibboleth!https://iam.cf.ac.uk/sp/shibboleth!zvmxrzixwj18dvunhwfpbdpvatk= 7 years ago.
PostgreSQL import log

Change History

Changed 7 years ago by https://idp.heanet.ie/idp/shibboleth!https://iam.cf.ac.uk/sp/shibboleth!zvmxrzixwj18dvunhwfpbdpvatk=

PostgreSQL import log

comment:1 Changed 7 years ago by smith@…

  • Milestone set to v1.2.0

comment:2 Changed 6 years ago by smith@…

  • Milestone changed from v1.2.0 to v1.2.2

comment:3 Changed 6 years ago by smith@…

  • Status changed from new to closed
  • Resolution set to fixed
  • Milestone changed from v1.2.2 to v1.2.1

We've seen this ourselves. Think it's an issue with length of name. We're switching to using the shorter names as the default (using event-name-limit.hbm.xml instead of event.hbm.xml the in MUA's database.xml. This solves this issue.

For those with existing databases, they can either switch to the short name version and migrate the data from the old tables to the new tables, or look at the updated database schema and add the missing indexes in manually.

Note: See TracTickets for help on using tickets.