Timeline for Select query with named slot lookups?
Current License: CC BY-SA 3.0
9 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Jan 7, 2015 at 15:40 | vote | accept | alancalvitti | ||
Jan 7, 2015 at 15:39 | comment | added | alancalvitti | You're right, I was A/B'ing to my original input data. Nice solution here, thanks. | |
Jan 7, 2015 at 0:17 | comment | added | WReach | @alancalvitti If I run your query against the exhibited input data, I get the same result as my query: the single entry for 00:12:27.9. That is correct since it is the only one between 00:12:15 and 00:38:49. Perhaps your screenshot was taken after using different data? | |
Jan 6, 2015 at 23:12 | comment | added | alancalvitti |
Why does it only return a single row in Q001 (compare to the output in my Q)
|
|
Jan 6, 2015 at 18:01 | comment | added | WReach | @alancalvitti Ah yes, my misunderstanding. Does my update help? | |
Jan 6, 2015 at 18:01 | history | edited | WReach | CC BY-SA 3.0 |
added the update in response to @alancalvitti's comment
|
Jan 6, 2015 at 17:20 | comment | added | alancalvitti |
Thanks again for the analysis. However, doesn't address limitations (2) and (3), namely VisitStartTime and VisitEndTime are only for use in the Select logic and should not appear in the output, and desired format is <|"Q001" -> {"Morae/Manual/Emr/Coder1Data" -> ...}, ...|> , ie, with Morae... key included. Ideally (2) and (3) should not be post-processing steps.
|
|
Jan 6, 2015 at 4:50 | history | edited | WReach | CC BY-SA 3.0 |
missing word
|
Jan 6, 2015 at 4:43 | history | answered | WReach | CC BY-SA 3.0 |