Evergreen

wrong version of asset.merge_record_assets() stored function

Bug #1758347 reported by Galen Charlton
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Evergreen
Fix Released
High
Unassigned
Evergreen 3.1.0

Bug Description

The schema update script from bug 1731960 had an out-of-date version of asset.merge_record_assets() that lacks the merge tracking changes introduced in bug 1744996.

The version of the function in 999.functions.global.sql is correct, so an additional schema update script will set things right.

Evergreen 3.1-rc

See original description
Tags: regression
Galen Charlton (gmc)
Changed in evergreen:
assignee: nobody → Galen Charlton (gmc)
Revision history for this message
Galen Charlton (gmc) wrote :

Given the nature of the problem and a desire to coordinate with merging the patch for bug 1758347, I've taken the liberty of pushing a fix directly to master and rel_3_0.

Changed in evergreen:
status: New → Fix Committed
assignee: Galen Charlton (gmc) → nobody
Revision history for this message
Jason Boyer (jboyer) wrote :

I was looking at this today and this change shouldn't go into rel_3_0. It looks like the merge tracking feature is rel_3_1 only. If 1108.schema.lp1758347_fix_merge_record_assets.sql is applied to a 3.0.X system merging will be broken until it's reverted.

Revision history for this message
Galen Charlton (gmc) wrote :

Reverted the error in rel_3_0. Thanks for the catch, Jason!

no longer affects: evergreen/3.0
description: updated
Evergreen Bug Maintenance (bugmaster)
Changed in evergreen:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.