This makes the schema version match the old upgrade, and adds a new upgrade file for anyone unlucky enough to have installed with the bad schema.
As it stands, while the logic is at least functional now, you will get an insert error if you 'add_only' something which is already there, rather than just a notice or warning, but maybe this is the intended behavior. If we decide we want to do something else, we will have to take that on separately.
Branch to fix is here:
http:// git.evergreen- ils.org/ ?p=working/ Evergreen. git;a=shortlog; h=refs/ heads/user/ dbwells/ lp1091831_ coded_value_ map_function_ fix
working/ user/dbwells/ lp1091831_ coded_value_ map_function_ fix
This makes the schema version match the old upgrade, and adds a new upgrade file for anyone unlucky enough to have installed with the bad schema.
As it stands, while the logic is at least functional now, you will get an insert error if you 'add_only' something which is already there, rather than just a notice or warning, but maybe this is the intended behavior. If we decide we want to do something else, we will have to take that on separately.