Skip to main content
12 events
when toggle format what by license comment
Oct 3, 2012 at 19:53 vote accept Matt Susevich
Oct 3, 2012 at 19:52 answer added Griffin timeline score: 3
Oct 3, 2012 at 19:49 comment added Matt Susevich @Griffin - Wow, really not one of my brighter moments haha. Much obliged, taking D_E_D out of the Partition worked. If you post as an answer and I'll accept.
Oct 3, 2012 at 19:47 comment added Griffin In that case, shouldn't the DIFF_ENCOUNTER_DATE not be in the partition?
Oct 3, 2012 at 19:31 comment added Matt Susevich In short, yes there may be multiple values. What I'm targeting is to take all of the CASE_SEQ values of each MEMBER_UPI and number them sequentially based off of the DIFF_ENCOUNTER_DATE. When there is a new CASE_SEQ for the same MEMBER_UPI, the numbering for NOTE_COUNTER should commence anew.
Oct 3, 2012 at 19:27 comment added Griffin If you are concerned about column ambiguity between #TMP_NOTES and RecordsBeingUpdated, you could alias the columns in RecordsBeingUpdated. (e.g.: SELECT MEMBER_UPI AS MU, ...)
Oct 3, 2012 at 19:22 comment added Griffin Is it possible for there to be multiple records keyed by MEMBER_UPI, CASE_SEQ, DIFF_ENCOUNTER_DATE? Just making sure I understand the requirements correctly. So, you would like to see NOTE_COUNTER increment within a grouping of M_U, C_S, and D_E_D, then restart for a new value. So you might have a sequence in NOTE_COUNTER like 1,2,3,1,1,1,2,3,4,...
Oct 3, 2012 at 18:07 history edited Matt Susevich CC BY-SA 3.0
Grammar fixes
Oct 3, 2012 at 18:01 history tweeted twitter.com/#!/StackCodeReview/status/253555469950521344
Oct 3, 2012 at 17:16 history edited Matt Susevich CC BY-SA 3.0
edited body
Oct 3, 2012 at 17:07 review First posts
Oct 3, 2012 at 17:18
Oct 3, 2012 at 17:06 history asked Matt Susevich CC BY-SA 3.0