INDEX user_type_context_idx is not generated when creating msgcntr db objects using auto.ddl=true
GENERAL
TESTING
GENERAL
TESTING
Description
is related to
Activity
Show:
Anthony Whyte March 22, 2011 at 1:13 AM
Merged to 2.8.x.
Bryan Holladay March 17, 2011 at 8:24 AM
r89922
removed the alter statements for contraints and added the oracle script
Michelle Wagner March 11, 2011 at 6:41 PM
Bryan Holladay added mysql index script - r89368
Anthony Whyte February 7, 2011 at 12:41 PMEdited
I've prioritized this ticket as a 2.8.0 blocker but I suspect that our ability to address this issue is constrained by Hibernate behavior (3.2.7-ga). However, it might be do well to create a "local" project script that includes this index and any others that should be run by new adopters if it is found that Hibernate fails to generate indexes on first start up.
Fixed
Created February 7, 2011 at 12:36 PM
Updated October 4, 2013 at 1:06 PM
Resolved March 17, 2011 at 8:24 AM
The 2.8.0 conversion scripts includes the following CREATE INDEX statement:
– Hibernate could have missed this index, if this fails, then the index may already be in the table
create index user_type_context_idx on MFR_PVT_MSG_USR_T (USER_ID(36), TYPE_UUID(36), CONTEXT_ID(36), READ_STATUS);
Doing a Liquibase compare between a MySQL 5.1 auto.ddl generated sakai-2.8.0-b04 db and a MySQL 5.1 2.7.1->2.8.0 converted db indicates that this index is not being created by Hibernate when generating msgcntr db objects using auto.ddl=true.
Missing Indexes:
user_type_context_idx unique on mfr_pvt_msg_usr_t(USER_ID, TYPE_UUID, CONTEXT_ID, READ_STATUS)