P4DTI issue job000355

TitleBugzilla integration ignores start_date parameter
Assigned userGareth Rees
DescriptionWhen you start the replicator for the first time, it doesn't replicate anything. It's supposed to replicate all changes since the start_date.
AnalysisA change since release 1.1.1 ensures that there is always a row in the p4dti_replications table. However, this breaks the start_date logic (which applies if the replicator has not run before, i.e. if there are no rows in the p4dti_replications table).
Work-around could be that the first row added to the p4dti_replications table should have the 'end' field be equal to the start_date. So there should be a function whose job is to add such a record to the p4dti_replications table if the table is empty and we should call this function in dt_bugzilla.init().
How foundmanual_test
EvidenceDiscovered during testing before release 1.1.2.
Introduced in1.1.2
Test procedure<http://www.ravenbrook.com/project/p4dti/master/test/test_p4dti.py>, section 8
Created byGareth Rees
Created on2001-07-16 13:35:59
Last modified byGareth Rees
Last modified on2001-12-10 19:50:08
History2001-07-16 GDR Created.


Change Effect Date User Description
14179 closed 2001-07-16 17:13:29 Gareth Rees Ensured that there's always a row in the replications table. On the first replication, this pretends that the last replication was on the start_date.