Florian Schmitz wrote: > > Hello List, > > we're currently migrating our live 7.5.00.26-instance to > 7.6.00.32 (32bit to 64bit). > > The following query worked fine under 7.5 : > SELECT distinct c.customerno AS Kundennummer,c.name AS > Kundenname FROM customer c order by c.customerno > > With 7.6 it gives a General error;-8013 POS(94) Order column > must be output column. > Is there a param to make this query (and propably others we > haven't tested yet) working again? >
No, there is no param to make this work again. For explanation: if a distinct is included, every order-by-column has to be part of the output. Unfortunately version 7.5 was not correct in this context, when having a reference-name for an output-column. We had to change a check in a way that in case of reference-name given, the reference-name has to be used in the order-by-clause, not the selected column itself. Now you have the problem to find out where such (in older versions seeming correct) clauses are used and should change it. We did not see that problem, meaning: we did not expect people having used this changed/corrected semantic and therefore we do not have a workaround and/or parameter to change it to the old behaviour. I am sorry for this wrong assumption. But there is no 'trick' to avoid changing this (and the other) select(s). I hope this will not cause too much trouble. Elke SAP Labs Berlin > Thanks alot, > > Flo > > -- > MaxDB Discussion Mailing List > For list archives: http://lists.mysql.com/maxdb > To unsubscribe: > http://lists.mysql.com/[EMAIL PROTECTED] > > -- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
