Literal factoid ordering changes when adding a start index

Bug #726236 reported by marcog
6
This bug affects 1 person
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
               regions, particularly on dry-land agricultural operations where the outside
               application of additional moisture is impossible, 3: is tumbledore, 4: is my
               complaint.
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
               where the outside application of additional moisture is impossible, 4: is a Bear

The order should remain the same when adding an index. I'm sure this is a regression.

Revision history for this message
Stefano Rivera (stefanor) wrote :

> I'm sure this is a regression.

A regression with SQLAlchemy 0.6 on postgres. Still worth fixing, though.

Changed in ibid:
importance: Undecided → Low
milestone: none → 0.2.0
status: New → Triaged
George Gill (ggilliii10)
description: updated
description: updated
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.