Opened 17 years ago
Closed 16 years ago
#1014 closed defect (fixed)
Issues listing data after removing items
Reported by: | Jari Häkkinen | Owned by: | Nicklas Nordborg |
---|---|---|---|
Priority: | trivial | Milestone: | BASE 2.8 |
Component: | core | Version: | trunk |
Keywords: | Cc: |
Description
In some cases listing of spot data fails for me. After deleting several analysis step that created extra values, and then redoing these steps, and then returning to the spot data view for closer examination of the extra values I get
ExtraValue[id=9] does not exist.
en no stack trace in tomcat log. The extra values do exist but has a new id since I created new extra values and the old ones where deleted. If I look at the same spot data as another user I do not have the issue.
Changing the columns to display does not make any change. Finally, by chance I selected to sort the list on the extra value column, see and behold, I get the listing I expect.
Change History (4)
comment:1 by , 17 years ago
Summary: | Issues listing spot data for a bioassay after removing items → Issues listing data after removing items |
---|
comment:2 by , 17 years ago
Milestone: | → BASE 2.x+ |
---|
comment:3 by , 16 years ago
Milestone: | BASE 2.x+ → BASE 2.8 |
---|---|
Owner: | changed from | to
Priority: | major → trivial |
Status: | new → assigned |
I'll add Reporter lists to the list of affected items. Since #1016 it is possible to filter with a reporter list.
comment:4 by , 16 years ago
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
(In [4405]) Fixes #1014: Issues listing data after removing items
This should fix the problems with reporter lists, extra values and annotations. I don't think it is possible to solve all problems with extended properties and raw data. The reason is that in some cases the query is built by parts of the code that doesn't know if it is generating a query for reporters/raw data or any other type of item.
This can happen when a user has chosen to display/sort on/filter on a column that is later removed. This is an issue in all listings for all kinds of columns that can be dynamically created and deleted, including:
In all cases the workaround is re-configure the list to make the problem go away. This is what can be tried: