Re: Unnexpected nonaggregated field error
Thank you.
It seems like ANY_VALUE is an efficient solution since it will minimize the additional overhead for resolving this peculiar situation. My issues are:
1. that it is for some reason not required when the statement is issued against any of the other TEN Censusyyyy databases in the system, only Census1911.
2. it is not supported by MariaDB and I cannot predict which DB will be deployed by a particular web provider. "purist" distros tend to use MariaDB because its license is less encumbered, and because they do not trust Oracle. I have not tested this code against MariaDB yet, but it is my understanding that MariaDB does not have the equivalent validation feature.
Of course I do not want to turn off the full group error because it is a valuable tool.
What documentation should I collect for a bug report?
Subject
Written By
Posted
Re: Unnexpected nonaggregated field error
October 01, 2016 06:03PM
Sorry, you can't reply to this topic. It has been closed.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion
of Oracle or any other party.