| Key: |
RHQ-917
|
| Type: |
Bug
|
| Status: |
Open
|
| Priority: |
Major
|
| Assignee: |
Unassigned
|
| Reporter: |
John Mazzitelli
|
| Votes: |
0
|
| Watchers: |
0
|
|
If you were logged in you would be able to see more operations.
|
|
|
RHQ Project
Created: 01/Oct/08 10:31 PM
Updated: 13/Oct/08 03:37 PM
|
|
| Component/s: |
Core Server
|
| Affects Version/s: |
1.1
|
| Fix Version/s: |
None
|
|
| Date of First Response: |
01/Oct/08 10:34 PM
|
|
If I update an operation definition, specifically, if I changed the name of an existing operation, the plugin metadata manager will treat this as a new operation with the "old" operation (with the previous name) needing to be deleted. However, to delete, it means that operation must not have any operation history rows related to it. If the old operation has been invoked before and the operation history still exists, a constraint violation will occur when the deletion is attempted.
Need to move the relationship of the history rows to point to the new operation definition so the old op definition can be deleted.
|
|
Description
|
If I update an operation definition, specifically, if I changed the name of an existing operation, the plugin metadata manager will treat this as a new operation with the "old" operation (with the previous name) needing to be deleted. However, to delete, it means that operation must not have any operation history rows related to it. If the old operation has been invoked before and the operation history still exists, a constraint violation will occur when the deletion is attempted.
Need to move the relationship of the history rows to point to the new operation definition so the old op definition can be deleted. |
Show » |
|
updating operation with a name change requires there to be 0 operation history rows
My idea would be to have old operations be marked "obsolete" instead of trying to delete them. Then we can keep the history available, but filter them from the runnable operations.