[progress Communities] [progress Openedge Abl] Forum Post: Re: Select Distinct Over Jdbc...

  • Thread starter Thread starter Jason Bailey
  • Start date Start date
Status
Not open for further replies.
J

Jason Bailey

Guest
Steve, That does group things together, as one would expect with a group statement, but using my example above, I want no rows with duplicate CUST_NUM values. In the above example, there are three rows with a CUST_NUM value of 4424 (Mary) and two rows with a CUST_NUM value of 3456 (John). I'd like to consolidate those results so that I'm only getting one row for 4424 (Mary) and only one row for 3456 (John). In a PostgreSQL or MySQL world, a 'SELECT DISTINCT' would do the trick. The problem is that (as I understand it), because OpenEdge thinks in terms of rows and not data sets, it just doesn't process this way. Does that make sense?

Continue reading...
 
Status
Not open for further replies.
Back
Top