Literal factoid ordering changes when adding a start index
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ibid |
Triaged
|
Low
|
Unassigned |
Bug Description
23:24 < marcog> tibid: literal tumbleweed
23:24 < tibid> marcog: 1: is a Bear, 2: has a significant effect on wind soil erosion in open
23:24 < marcog> tibid: literal tumbleweed #1
23:24 < tibid> marcog: 1: is tumbledore, 2: is my complaint., 3: has a significant effect on wind
soil erosion in open regions, particularly on dry-land agricultural operations
The order should remain the same when adding an index. I'm sure this is a regression.
description: | updated |
description: | updated |
> I'm sure this is a regression.
A regression with SQLAlchemy 0.6 on postgres. Still worth fixing, though.