Robert Klemme wrote: > > Hi, > > > > consider this query > > > > SELECT TA1.propvalue AS COL1, VALUE(TA4.map_value, > TA1.propvalue) AS COL2 > > FROM ag_site TA1 LEFT OUTER JOIN mp_1149664790259_1 TA4 ON > > TA1.propvalue=TA4.map_key, ag_url TA2, v_ag_hourlymaster TA3 > > WHERE TA1.indexid=TA2.siteid AND TA2.urlid=TA3.urlid AND ( > > TA3.applianceid IN ( 1, 22 ) ) > > GROUP BY TA1.propvalue, VALUE(TA4.map_value, TA1.propvalue) > > ORDER BY TA1.propvalue ASC > > > > When run on 7.5.00.18 it seems to ignore the GROUP BY clause. > > Duplicate combinations of COL1 and COL2 are seen in the > result set. I > > checked change history of recent 7.5 versions but could not find a > > clear match with this problem description. Any ideas? > > > > Kind regards > > > > robert > > > > -- > > Have a look: http://www.flickr.com/photos/fussel-foto/ > >
Hi, with the help of Robert I was able to reproduce the problem and find a bug within the MaxDB kernel within group by handling in outer joins if no set function is given. We will fix this bug with one of the next patches. For detailed information in which patch this fix will be included have a look at http://www.sapdb.org/webpts?wptsdetail=yes&ErrorType=0&ErrorID=1000049 As a workaround you could use distinct instead of group by clause. Thanks to Robert for reporting this bug. Kind regards Holger -- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
