I think that the global collected_info sequence is incrementing "without holes", but for any single object collecting informations the list of collections that relate to it can look like gruyere chese - exactly because the id is global and not per-object.
Unfortunately the current info-collection related fetches are made in such a way that it is quite easy to use the mechanism for polls, but almost impossible to use it for eg. comments.
Luckily it is not very hard to add your own, improved, info-collection fetches that will execute the correct queries in the db and fetch all collections pertaining to a given object (if that was the final goal, that is)
Otoh, can collections be deleted? That would be a handy explanation!
Principal Consultant International Business
Member of the Community Project Board
<i>[...] but for any single object collecting informations the list of collections that relate to it can look like gruyere chese [...]</i> yes, like an very old one ;-) , this was my first thought, but there is only one info collector, and the information collection / collector - holes are visible in database, too.
And deleting, no, nobody.
Anybody with similar symptoms?
Not this: http://issues.ez.no/9745
Perhaps this: http://issues.ez.no/10105 at kernel/content/collectedinfo.php the version 3.8.6 was with this error:
