You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@continuum.apache.org by "Wendy Smoak (JIRA)" <ji...@codehaus.org> on 2009/06/25 02:33:55 UTC
[jira] Created: (CONTINUUM-2277) SCMRESULT records are never
deleted (unconfirmed)
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
[jira] Issue Comment Edited: (CONTINUUM-2277) SCMRESULT records are
never deleted (unconfirmed)
Posted by "Maria Catherine Tan (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/CONTINUUM-2277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=181561#action_181561 ]
Maria Catherine Tan edited comment on CONTINUUM-2277 at 6/25/09 9:10 PM:
-------------------------------------------------------------------------
Yes this only affects 1.3.1.
Using data management tool, the records will not be restored when you upgrade from 1.3.1 to 1.3.2 or later. However, we currently have an issue using data management tool to upgrade from 1.3.1 to 1.3.x. See http://jira.codehaus.org/browse/CONTINUUM-2163 and I already submitted the patch for that in http://jira.codehaus.org/browse/MODELLO-200, which we need before we can do the general release for 1.3.x series.
Using manual upgrade will require the user to manually delete the scmResult column from the Project table.
was (Author: ctan):
Yes this only affects 1.3.1.
Using data management tool, the records will not be restored when you upgrade from 1.3.1 to 1.3.2 or later. However, we currently have an issue using data management tool to upgrade from 1.3.1 to 1.3.x. See http://jira.codehaus.org/browse/CONTINUUM-2163 and I already submitted the patch for that in http://jira.codehaus.org/browse/MODELLO-200.
Using manual upgrade will require the user to manually delete the scmResult column from the Project table.
> 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
[jira] Commented: (CONTINUUM-2277) SCMRESULT records are never
deleted (unconfirmed)
Posted by "Maria Catherine Tan (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/CONTINUUM-2277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=181561#action_181561 ]
Maria Catherine Tan commented on CONTINUUM-2277:
------------------------------------------------
Yes this only affects 1.3.1.
Using data management tool, the records will not be restored when you upgrade from 1.3.1 to 1.3.2 or later. However, we currently have an issue using data management tool to upgrade from 1.3.1 to 1.3.x. See http://jira.codehaus.org/browse/CONTINUUM-2163 and I already submitted the patch for that in http://jira.codehaus.org/browse/MODELLO-200.
Using manual upgrade will require the user to manually delete the scmResult column from the Project table.
> 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
[jira] Updated: (CONTINUUM-2277) SCMRESULT records are never
deleted (unconfirmed)
Posted by "Wendy Smoak (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/CONTINUUM-2277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Wendy Smoak updated CONTINUUM-2277:
-----------------------------------
Fix Version/s: Reviewed
MODELLO-200 is fixed, have we picked this up in Continuum yet?
If so, a note in the docs about when you might need to and how to delete these records should be sufficient.
> 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
> Fix For: Reviewed
>
>
> 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
[jira] Commented: (CONTINUUM-2277) SCMRESULT records are never
deleted (unconfirmed)
Posted by "Wendy Smoak (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/CONTINUUM-2277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=181436#action_181436 ]
Wendy Smoak commented on CONTINUUM-2277:
----------------------------------------
Thanks, Marica. Did this only affect version 1.3.1?
If you upgrade from 1.3.1 to 1.3.2 or later, will it remove the records that shouldn't be there?
If not, how do you clean it up manually?
> 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
[jira] Commented: (CONTINUUM-2277) SCMRESULT records are never
deleted (unconfirmed)
Posted by "Maria Catherine Tan (JIRA)" <ji...@codehaus.org>.
[ 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