Patrick Buchinger wrote: > > hello! > > i discovered the following problem when i was updating from > 7.3.0.24 to > 7.3.0.34 (on a redhat 9.0 maschine): > > in 7.3.0.24 the following query worked without problems: > > SELECT max(id) + 1 newId FROM table HAVING NOT max(id) + 1 IS NULL > > > > in 7.3.0.34 the same query results in an error: "Column must > be in group > column: NEWID > > why should i put a column which is part of an aggregate-function into > group columns? > but no matter which columns i put into "group by", SapDB always > complains about missing group columns. > > has anyone an explanation?
Hi, thank you for reporting, the IS NULL-comparison causes the new trouble. Will be fixed with the next version. In case id is NULL or >= 0, one could change the HAVING-clause to HAVING max(id) >=0, resulting in false if max(id) IS NULL Elke SAP Labs Berlin _______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general
