Task #2901 (closed)
Opened 9 years ago
Closed 7 years ago
Possibly add index to field column
| Reported by: | jamoore | Owned by: | |
|---|---|---|---|
| Priority: | critical | Milestone: | OMERO-4.4 |
| Component: | Model | Version: | n.a. |
| Keywords: | n.a. | Cc: | cxallan, jburel, jrswedlow, ajpatterson |
| Resources: | n.a. | Referenced By: | n.a. |
| References: | n.a. | Remaining Time: | n.a. |
| Sprint: | n.a. |
Description
Assumptions about the number of samples per well may need re-thinking. During a conversation at BII2010, a Columbus user said that 100s of fields or more may not be too many. (100 was discussed because some software currently arbitrarily limits to that number)
The use case was getting around limits to long time-series on HCS systems.
Change History (7)
comment:1 Changed 8 years ago by jmoore
comment:2 Changed 8 years ago by jmoore
Is there anything we want/can do on this front for 4.3?
comment:3 Changed 8 years ago by jmoore
Referencing ticket #2568 has changed sprint.
comment:4 Changed 8 years ago by jmoore
Referencing ticket #2568 has changed sprint.
comment:5 Changed 8 years ago by jmoore
Referencing ticket #4891 has changed sprint.
comment:6 Changed 7 years ago by jburel
- Cc ajpatterson added
comment:7 Changed 7 years ago by jmoore
- Milestone changed from Unscheduled to OMERO-Beta4.4
- Resolution set to fixed
- Status changed from new to closed
There's currently a UNIQUE INDEX on (well, well_index) on the wellsample table. Seems like this would suffice. Closing.
Note: See
TracTickets for help on using
tickets.
You may also have a look at Agilo extensions to the ticket.
Referencing ticket #2568 has changed sprint.