When dumping data into fixtures via the piccolo fixtures dump command, no ORDER BY is specified.
|
data = await table_class.select().run() |
It's not a huge problem, but it is annoying when:
- You dump a fixture
- Add it to Git
- Later replace the fixture with a new version
The diff could be much larger than if a strict order was enforced.
We could just always order by primary key. Or add some way of the user specifying the sort order.
When dumping data into fixtures via the
piccolo fixtures dumpcommand, noORDER BYis specified.piccolo/piccolo/apps/fixtures/commands/dump.py
Line 49 in fc2a650
It's not a huge problem, but it is annoying when:
The diff could be much larger than if a strict order was enforced.
We could just always order by primary key. Or add some way of the user specifying the sort order.