Fix LT-21976: Merge Create dates when merging entries#334
Conversation
* Store the date at the start of the import and use it in entry creation. We need to have a consistent date recorded to determine if we read a date from the xml data or not. * Add a function to return the newest date that was actually read from the xml data.
imnasnainaec
left a comment
There was a problem hiding this comment.
Reviewable status: 0 of 2 files reviewed, 1 unresolved discussion
src/SIL.LCModel/Application/ApplicationServices/XmlImportData.cs line 491 at r1 (raw file):
return; } if (leNew.DateCreated == m_importDate)
Would it be worth having >= m_importDate on these two checks just in case a .DateCreated is from DateTime.Now on a system with a different clock?
|
Previously, imnasnainaec (D. Ror.) wrote…
No, I don't think it is worth it. The real concern here is retaining data coming in from the import, if we end up with created dates in the future that is a GIGO issue for the user that doesn't cause any real issues for our functionality. |
23624cf to
b8d41e8
Compare
c23944e to
b2946b0
Compare
b2946b0 to
913b234
Compare
imnasnainaec
left a comment
There was a problem hiding this comment.
(but I don't have "Approve" permissions)
Reviewed 1 of 2 files at r1, 1 of 1 files at r6, all commit messages.
Reviewable status:complete! all files reviewed, all discussions resolved (waiting on @jasonleenaylor)
tests/SIL.LCModel.Tests/Application/ApplicationServices/XmlImportDataTests.cs line 856 at r6 (raw file):
"</FwDatabase>" + Environment.NewLine )) using(var writer = new StringWriter(sbLog))
(found it!)
This change is