| Title | Filespecs and fixes aren't replicated properly from TeamTrack to Perforce |
| Status | closed |
| Priority | nice |
| Assigned user | Gareth Rees |
| Organization | Ravenbrook |
| Description | Changes to filespecs and fixes aren't replicated properly from TeamTrack to Perforce, when the user edits them from TeamTrack, say. |
| Analysis | When a filespec or fix record is replicated from TeamTrack to Perforce, the last replicated time in the VCACTIONS table needs to be updated. But it isn't updated. So a filespec or fix that's edited in TeamTrack will be repeatedly replicated mistakenly. This may cause a conflict. However, it turns out that TeamTrack puts a record in the CHANGES table whenever a filespec or fix is added, edited or deleted. So by looking in the CHANGES table rather than by comparing dates in the VCACTIONS table, the replicator can do the right thing. GDR 2000-11-30. |
| How found | inspection |
| Evidence | None as yet. |
| Created by | Gareth Rees |
| Created on | 2000-10-19 15:14:03 |
| Last modified by | Gareth Rees |
| Last modified on | 2001-12-10 18:58:01 |
| History | 2000-10-19 GDR Created based on entry in to do list on whiteboard. 2000-11-21 RB Improved title and copied to description. Downgraded to "Nice" because we're probably not going to provide this feature. Might become more important if TeamTrack fix their end. 2000-11-30 GDR Added analysis. Closed the job. |
| Change | Effect | Date | User | Description |
|---|---|---|---|---|
| 5134 | closed | 2000-11-29 20:41:35 | Gareth Rees | Put the correct date in changelists and fixes. As a consequence of this, we can't use TIME1 > TIME2 as a way of finding changed fixes and filespecs. However, TeamTrack puts a record in the CHANGES table when a fix is edited or added so we can use that instead. |