[
http://jira.codehaus.org/browse/CONTINUUM-2277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=181430#action_181430
]
Maria Catherine Tan commented on CONTINUUM-2277:
------------------------------------------------
This is certainly a bug in 1.3.1. The scm results are only deleted when you
delete the project itself. Also noticed that there are still some scm results
that are left behind even if you already deleted the whole project group. (This
might be caused by the changes made for transient state)
In 1.3.2 up, this was fixed. The update scm results related to BUILDRESULT gets
deleted when you delete the build result. The checkout scm result related to
PROJECT gets deleted once the project is also deleted.
> SCMRESULT records are never deleted (unconfirmed)
> -------------------------------------------------
>
> Key: CONTINUUM-2277
> URL: http://jira.codehaus.org/browse/CONTINUUM-2277
> Project: Continuum
> Issue Type: Bug
> Components: Database
> Affects Versions: 1.3.1
> Reporter: Wendy Smoak
>
> I have an unconfirmed report of a 1.3.1 instance where the SCMRESULT table
> has far more records than it should, as if they are getting orphaned or not
> getting deleted appropriately.
> According to the schema, SCMRESULT is related to BUILDRESULT, so if you
> delete the build results, the scm results should also go away.
> http://wsmoak.net/continuum/schemaspy/1.3.1/SA/tables/SCMRESULT.html
> I haven't had time to test this, but wanted to record it so it doesn't get
> forgotten.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
