NoPublic, bureaucrat, administrator
6,632
edits
Changes
no edit summary
Duplicate enumvalues cause import issues i.e. empty fields, which are difficult to detect due to there are no error messages
This query should be exported as documentation of the values of the four affected enumcategoriesthat the upgrade script wrongly creates duplicates for (This might be fixed now/NAA 2014-10-07):
<pre>
SELECT DISTINCT
imsmaenum.enumvalue ASC
</pre>
The upgrade scripts wrongly add values to the four enumcategories so duplicates are created (This might be fixed now/NAA 2014-10-07). <br/>The upgrade scripts also set some of the existing enumvalues to '''inactive'''. Since all countries may have different duplicates and different options set to inactive there is no fit-all solution and therefore the duplicates enumvalues are best fixed semi-manually. <br/><br/>
[[Image: Duplicate enumvalue1.png | 350px]] <br/>
''Example of enumcategory with duplicates (Query 1)'' <br/> <br/>
