[p4dti-discussion] P4DTI continues to repeat replication of entire bugzilla db

[Scott Taylor]

using:
   bugzilla-2.20
   p4dti-2.3.0-1.i386
   perforce 2005.2

As my subject title describes, I am seeing an unfortunate issue where
p4dti likes to replicate my entire bug db over and over again.  There
are approximately 8K bugs which causes a significant performance hit
to bugzilla every time p4dti wants to do this (of course now it has
long been disabled).

I had p4dti working correctly until recently when my company decided
to update to perforce 2005.2 and modify bugzilla to add a couple more
fields (which are not part of the jobspec nor do I need replicated). 
Since I could not locate the source of this issue, I was forced to do
the trusty uninstall/reinstall method.  In my uninstall, I removed the
patch, drop the p4dti tables, and remove all related jobs.  I then
proceeded with what I believe is a 'clean' install.  Of course after
all this I am still encountering the same issue.

What I see is normal p4dti messages indicating they are replicating
the bug and then the occasional p4dti messages that the job ## is
being overwriting by issue ## because p4dti believes they have changed
when in fact nothing did.  The replications are being tracked in the
p4dti tables, however in p4dti_bugs table I am seeing something
strange.  The p4dti_bugs field 'migrated' continues to remain NULL
after it replicates to perforce jobs.  By looking at the field's
details, a datetime should be inserted here.

Finally some questions....

Has anyone else experienced this issue?

Is there a problem with the p4dti_bugs migrated field?  If so, any
suggestions on how I can troubleshoot or fix it?

Is this a compatibility issue with perforce 2005.2?


I appreciate any help!

Thanks - Scott