Details
-
Type:
Story
-
Status: Done
-
Resolution: Done
-
Fix Version/s: None
-
Component/s: butler
-
Labels:None
-
Story Points:1
-
Epic Link:
-
Sprint:DB_X16_03
-
Team:Data Access and Database
Description
Backwards compatible behavior is that when butler returns a single item, it is NOT in a list. A recent change (when the Repository class was added) broke this behavior.
Change it back so that if an operation in repository would return a list with a single item, it pulls it from the list.
Note this is only related to the case where a repository's parentJoin field is set to 'outer' and since no one is using this yet (they should not be, anyway) then the point is moot.
Attachments
Issue Links
- blocks
-
DM-5632 test run coaddDriver and multiBandDriver with DECam data
- Done
Activity
Field | Original Value | New Value |
---|---|---|
Epic Link |
|
Rank | Ranked higher |
Assignee | Nate Pease [ npease ] |
Status | To Do [ 10001 ] | In Progress [ 3 ] |
Sprint | DB_X16_03 [ 204 ] |
Team | Data Access and Database [ 10204 ] |
Description |
Backwards compatible behavior is that when butler returns a single item, it is NOT in a list. A recent change (when the Repository class was added) broke this behavior.
Change it back so that if an operation in repository would return a list with a single item, it pulls it from the list. |
Backwards compatible behavior is that when butler returns a single item, it is NOT in a list. A recent change (when the Repository class was added) broke this behavior.
Change it back so that if an operation in repository would return a list with a single item, it pulls it from the list. Note this is only related to the case where a repository's parentJoin field is set to 'outer' and since no one is using this yet (they should not be, anyway) then the point is moot. |
Status | In Progress [ 3 ] | Reviewed [ 10101 ] |
Resolution | Done [ 10000 ] | |
Status | Reviewed [ 10101 ] | Done [ 10002 ] |
What is the long-term plan for this? If an operation would normally return a list of items but only happens to find one, I'd much rather have it be a list of one item, for the sake of consistency. On the other hand, if the operation intrinsically returns a single item, e.g. butler.get("calexp", dataId) then it should not be a list.