Feb 6, 2017 4:25:07 PM by Dan Hotka
This is a companion discussion topic for the original entry at https://blog.toadworld.com/2017/02/06/oracle-behavior-differences-between-releases
This is a companion discussion topic for the original entry at https://blog.toadworld.com/2017/02/06/oracle-behavior-differences-between-releases
The reason GROUP BY no longer resulted in a default sort in Oracle 10.2 is that Oracle started using a hash value for the grouping rather than the columns. Many people relied on that default sort and were upset with the change. Oracle documentation has always stated that no order is guaranteed unless the SQL contains an ORDER BY clause. Even their documentation prior to 10 stated this.