Ticket Change Details
Not logged in
Overview

Artifact ID: ec4fc9fec9336d0a573cb5a0df16fde0311f8e8f
Ticket: 9b8333b29826deba9ddd6d3e4c6b26fc70e06e68
Cannot pull the up to date 'ticket' configuration
User & Date: drh 2011-04-27 12:17:35
Changes

  1. Appended to comment:
    
    
    <hr /><i>drh added on 2011-04-27 12:17:35 UTC:</i><br />
    Check-in [1654456ef5aa8d38c809414a5345bd7f7e76d3c7] adds an "mtime" column
    to the table that holds report formats so that a "configuration sync"
    operation will always take the most recently edited report format from
    the two repositories being synced.  This should fix the problem described
    here.
    
    Note, however, that a 
    [/event/a1f9f17b603022c2b032bc3 | irreversible schema change]
    occurs when upgrading to the new version.  And you need to upgrade all
    participating repositories before the fix will take effect.
    
    Note also that when upgrading the "mtime" field is initialized to the
    time of the upgrade.  So after upgrading two repos A and B, the first
    time you do a configuration sync, the one that was updated second will
    have the most recent mtime values on all entries and hence its report
    formats will always dominate over the report formats in the other 
    repository.  So be careful that you do not overwrite report formats
    (or other configuration information such as user passwords and capabilities)
    that you care about.  Upgrade the definitive repository last.
    
  2. resolution changed to: "Fixed"
  3. status changed to: "Fixed"