diff options
| author | Florian Apolloner <florian@apolloner.eu> | 2018-10-21 20:42:34 +0200 |
|---|---|---|
| committer | Florian Apolloner <apollo13@users.noreply.github.com> | 2018-10-21 22:05:06 +0200 |
| commit | c53af5661313079d022553b6c775e6c4f8d34927 (patch) | |
| tree | 0481c3ba950ea27a5e7a1754ff156a26eee0c88e /tests/postgres_tests/array_default_migrations/0002_integerarraymodel_field_2.py | |
| parent | e127ef62deaf6348eb00038f2280ae669d1019d6 (diff) | |
Fixed #29847 -- Ensured proper ordering in queries.
Even though good databases tend to keep the result sorted by the/one
window expression and the planners are smart enough to not resort if not
required, it is not valid to rely on this.
MariaDB specifically did return whatever order it wanted, which is
completely okay. Now we sort towards the expected data for all databases.
Diffstat (limited to 'tests/postgres_tests/array_default_migrations/0002_integerarraymodel_field_2.py')
0 files changed, 0 insertions, 0 deletions