Bug #119 (closed)
RenderingDef possibly needs a UNIQUE on (pixels, experimenter)
| Reported by: | jamoore | Owned by: | cxallan |
|---|---|---|---|
| Priority: | minor | Cc: | cxallan, jburel |
| Sprint: | n.a. | ||
| Total Remaining Time: | n.a. |
Description (last modified by jmoore)
Currently the DB is allowing multiple RenderingDefs per user, which causes the queries in PixelsImpl to throw a NonUniqueResultException.
Change History (7)
comment:1 Changed 18 years ago by jmoore
- Description modified (diff)
comment:2 Changed 18 years ago by jmoore
- Milestone changed from Unscheduled to 3.0-M4
Rescheduling with #334
comment:3 Changed 17 years ago by jmoore
- Milestone changed from 3.0-Beta2 to 3.0-Beta3
comment:4 Changed 16 years ago by jmoore
This is no longer an issue, correct?
comment:5 Changed 16 years ago by jmoore
- Owner changed from jmoore to callan
Chris, I assume this will be in all your RE fixes. Passing.
comment:6 Changed 16 years ago by cxallan
- Resolution set to invalid
- Status changed from new to closed
As we will be accepting more than one rendering definition per user, per pixels this is now invalid.
comment:7 Changed 16 years ago by cxallan
- Cc changed from callan,jburel to callan, jburel
- Version 3.0-M1 deleted
Additional features are now available that further invalidate this in r2344.
Note: See
TracTickets for help on using
tickets.
You may also have a look at Agilo extensions to the ticket.
Does this need to get moved into M2/iteration4?