[RevisionMachine] ArticleIndex and ChronoIndex procuce multiple entries for some ArticleIDs

[GoogleCodeExporter]

The ArticleIndex and ChonoIndex produce multiple entries for some ArticleIDs.
This is a problem - ArticleID is the primary key of the respective tables and 
must be unique.
The duplicate rows are omitted upon import.

Info for the ArticleIndex:
The field "FullRevisionPKs" should contain all PKs of full revisions.
However, in reality, we have several entries for the article each with a 
different FullRevisionPK. The other fields are identical.

Ramifications:
The issue probably causes performance issues, as the first FullRevision is 
found - not the nearest. It should not affect accurancy.

For the ChronoIterator, ramifications are unknown.

Original issue reported on code.google.com by oliver.ferschke on 24 Jan 2012 at 10:42

[GoogleCodeExporter]

Side note:
Of course it SHOULD be normalized - no data structured in the database. As a 
first step, a fix would be enough. In the long run, the fields containing 
structured data should be normalized.

Original comment by oliver.ferschke on 24 Jan 2012 at 10:45

[GoogleCodeExporter]

Original comment by oliver.ferschke on 24 Jan 2012 at 10:47

• Added labels: Milestone-Release1.0

[GoogleCodeExporter]

Maybe use RevisionPK from the revision Index instead of RevisionPKs from the 
article index.

Original comment by oliver.ferschke on 24 Jan 2012 at 11:15

[GoogleCodeExporter]

See Issue 76

Original comment by oliver.ferschke on 26 Jan 2012 at 10:00

[GoogleCodeExporter]

While the RevisionPK should still be exchanged with the RevisionID and the 
tables should all be normalized, the problem reported here was a false alarm. 
Everything should be alright.

Original comment by oliver.ferschke on 27 Jan 2012 at 7:11

• Changed state: Invalid

[GoogleCodeExporter]

Original comment by oliver.ferschke on 16 Feb 2012 at 1:26

• Removed labels: Milestone-Release1.0