as part of the upgrade script for converting releases to nodes (see http://drupal.org/node/83339#comment-137458) i discovered that there are 2622 issue comments refer to a rid (release id) that doesn't exist in the {project_releases} table. there are 462 distinct rids that are missing from {project_releases}. i attached a list of them here: http://drupal.org/files/issues/project_release_missing.txt
to potentially help figure out what's going on, here's another copy of this table, but with a "pid" column added -- the project id of the issue that these comments came from. this copy is grouped by pid. i'll do another that groups by rid in the next attachment.
i wanted to submit this as a separate issue since it's not directly part of that other thing, and there's potentially a bug in project that needs to be found/fixed that's causing this problem...
| Comment | File | Size | Author |
|---|---|---|---|
| #3 | drupal.org.project_comments_conversion_errors.mysql | 52.31 KB | dww |
| #2 | drupal.org.project_releases_missing_pids_unique.mysql | 8.67 KB | dww |
| #1 | project_release_missing_rid_pid.txt | 11.23 KB | dww |
| project_release_missing_pid_rid.txt | 11.23 KB | dww |
Comments
Comment #1
dwwhere's the copy of the same data, but grouped by rid, not pid.
Comment #2
dwwif you want to play with this data yourself, here's a mysqldump of the {project_releases_missing} table.
Comment #3
dwwand here's a mysqldump of the table for all the project issues that couldn't be converted by the update script form http://drupal.org/node/83339 because of these missing rids.
cid = comment id (e.g. from {project_comments} table)
pid = project id (e.g. the 'pid' from {project_issues} table, or the nid from {project_projects})
old_rid = rid variable from the data->old array in the serialized 'data' field from {project_comments} (the old value of rid that this particular issue is changing).
new_rid = rid variable from the data->new array in the serialized 'data' field from {project_comments} (the new value of rid that this particular issue is trying to set the version to).
Comment #4
dwwafter brief discussion in IRC w/ killes, decided we're not going to fix this.
a) it doesn't *really* hurt anything (so long as the upgrade to releases-as-nodes clears out these bogus rids and sets them to 0).
b) it'll probably be a huge time sink to attempt to understand what caused this corruption
therefore, it's not worth it. we all have more pressing matters to attend to. ;)