| 176 | | | | results given by accessing the relation field. You can | |
| 177 | | | | either use a string or a list of strings, each | |
| 178 | | | | corresponding to the name of a field in the target | |
| 179 | | | | entity. These field names can optionally be prefixed | |
| 180 | | | | by a minus (for descending order). | |
| | 176 | | | results given by accessing the relation field. | |
| | 177 | | | Note that this sort order is only applied when loading | |
| | 178 | | | objects from the database. Objects appended to the | |
| | 179 | | | collection afterwards are not re-sorted in-memory on | |
| | 180 | | | the fly. | |
| | 181 | | | This argument accepts either a string or a list of | |
| | 182 | | | strings, each corresponding to the name of a field in | |
| | 183 | | | the target entity. These field names can optionally be | |
| | 184 | | | prefixed by a minus (for descending order). | |
| 281 | | | | results given by accessing the relation field. You can | |
| 282 | | | | either use a string or a list of strings, each | |
| 283 | | | | corresponding to the name of a field in the target | |
| 284 | | | | entity. These field names can optionally be prefixed | |
| 285 | | | | by a minus (for descending order). | |
| | 285 | | | results given by accessing the relation field. | |
| | 286 | | | Note that this sort order is only applied when loading | |
| | 287 | | | objects from the database. Objects appended to the | |
| | 288 | | | collection afterwards are not re-sorted in-memory on | |
| | 289 | | | the fly. | |
| | 290 | | | This argument accepts either a string or a list of | |
| | 291 | | | strings, each corresponding to the name of a field in | |
| | 292 | | | the target entity. These field names can optionally be | |
| | 293 | | | prefixed by a minus (for descending order). | |