fresh install with auto.ddl does not create some SAM_ASSESSMENTGRADING_T indexes

Description

fresh install with auto.ddl does not create some SAM_ASSESSMENTGRADING_T indexes

https://sakaiproject.atlassian.net/browse/SAK-10441

https://sakaiproject.atlassian.net/browse/SAK-8432

in a database that is created with auto.ddl, the indexes for SAM_ASSESSMENTGRADING_T look like:

mysql> show indexes from SAM_ASSESSMENTGRADING_T; +-------------------------+------------+---------------------------+--------------+-----------------------+-----------+-------------+----------+--------+------+------------+---------+---------------+ | Table | Non_unique | Key_name | Seq_in_index | Column_name | Collation | Cardinality | Sub_part | Packed | Null | Index_type | Comment | Index_comment | +-------------------------+------------+---------------------------+--------------+-----------------------+-----------+-------------+----------+--------+------+------------+---------+---------------+ | sam_assessmentgrading_t | 0 | PRIMARY | 1 | ASSESSMENTGRADINGID | A | 0 | NULL | NULL | | BTREE | | | | sam_assessmentgrading_t | 1 | SAM_PUBLISHEDASSESSMENT_I | 1 | PUBLISHEDASSESSMENTID | A | 0 | NULL | NULL | | BTREE | | | +-------------------------+------------+---------------------------+--------------+-----------------------+-----------+-------------+----------+--------+------+------------+---------+---------------+ 2 rows in set (0.00 sec)

what it should look like, e.g. with auto.ddl=false and the conversion scripts have been run manually over the years.

mysql> show indexes from SAM_ASSESSMENTGRADING_T; +-------------------------+------------+-----------------------------+--------------+-----------------------+-----------+-------------+----------+--------+------+------------+---------+---------------+ | Table | Non_unique | Key_name | Seq_in_index | Column_name | Collation | Cardinality | Sub_part | Packed | Null | Index_type | Comment | Index_comment | +-------------------------+------------+-----------------------------+--------------+-----------------------+-----------+-------------+----------+--------+------+------------+---------+---------------+ | sam_assessmentgrading_t | 0 | PRIMARY | 1 | ASSESSMENTGRADINGID | A | 2269693 | NULL | NULL | | BTREE | | | | sam_assessmentgrading_t | 1 | SAM_ASSGRAD_AID_PUBASSEID_T | 1 | AGENTID | A | 116698 | NULL | NULL | | BTREE | | | | sam_assessmentgrading_t | 1 | SAM_ASSGRAD_AID_PUBASSEID_T | 2 | PUBLISHEDASSESSMENTID | A | 2092453 | NULL | NULL | | BTREE | | | | sam_assessmentgrading_t | 1 | SAM_PUBLISHEDASSESSMENT_I | 1 | PUBLISHEDASSESSMENTID | A | 91110 | NULL | NULL | | BTREE | | | | sam_assessmentgrading_t | 1 | SAM_AG_AGENTID_I | 1 | AGENTID | A | 131011 | NULL | NULL | | BTREE | | | +-------------------------+------------+-----------------------------+--------------+-----------------------+-----------+-------------+----------+--------+------+------------+---------+---------------+ 5 rows in set (0.16 sec)

Activity

Show:

Austin June 30, 2022 at 9:02 PM

I retested with 22.x and sam_assessmentgrading_t is missing both SAM_ASSGRAD_AID_PUBASSEID_T and SAM_AG_AGENTID_I

 

with 23.x sam_assessmentgrading_t is only missing SAM_AG_AGENTID_I, and as mentioned before, SAM_GRADINGSUMMARY_T shouldn’t have the SAM_AG_AGENTID_I index or maybe both should have them?

Austin June 9, 2022 at 7:57 PM

it looks like the fix in https://sakaiproject.atlassian.net/browse/SAK-12148#icft=SAK-12148 added the index to a different table, SAM_GRADINGSUMMARY_T

whereas, in this jira, it should have been added to sam_assessmentgrading_t

Austin May 6, 2022 at 12:05 AM

Austin May 6, 2022 at 12:04 AM

the https://sakaiproject.atlassian.net/browse/SAK-12148 patch now includes the fix for the SAM_AG_AGENTID_I index

Austin May 5, 2022 at 7:08 PM

This is partially fixed by https://sakaiproject.atlassian.net/browse/SAK-12148

However, the SAM_AG_AGENTID_I index still wasn’t created on startup after applying that patch.

Details

Priority

Affects versions

Assignee

Reporter

Created May 4, 2022 at 10:45 PM
Updated June 30, 2022 at 9:02 PM