BlackForestBytes/goext
20
0
Fork 0
Code Actions

v0.0.423 fix createPaginationPipeline - different primary and secondary sort keys broke mongo ??!?? - it actually only sorted by the secondary condition (ignoring the primary?)
All checks were successful
Build Docker and Deploy / Run goext test-suite (push) Successful in 1m32s
Details

Browse Source
This commit is contained in:
Mike Schwörer 2024-03-24 15:25:52 +01:00
parent 8bf3a337cf
commit 6c4af4006b
Signed by: Mikescher
GPG Key ID: D3C7172E0A70F8CF
2 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
goextVersion.go
View File

@ -1,5 +1,5 @@
package goext
const GoextVersion = "0.0.422"
const GoextVersion = "0.0.423"
const GoextVersionTimestamp = "2024-03-23T20:29:46+0100"
const GoextVersionTimestamp = "2024-03-24T15:25:52+0100"

4
wmo/queryList.go
View File

@ -171,7 +171,7 @@ func createPaginationPipeline[TData any](coll *Coll[TData], token ct.CursorToken
bson.M{*fieldSecondary: bson.M{"$gt": valueSecondary}},
}})
sort = append(sort, bson.E{Key: fieldPrimary, Value: +1})
sort = append(sort, bson.E{Key: *fieldSecondary, Value: +1})
} else if *sortSecondary == ct.SortDESC {
@ -181,7 +181,7 @@ func createPaginationPipeline[TData any](coll *Coll[TData], token ct.CursorToken
bson.M{*fieldSecondary: bson.M{"$lt": valueSecondary}},
}})
sort = append(sort, bson.E{Key: fieldPrimary, Value: -1})
sort = append(sort, bson.E{Key: *fieldSecondary, Value: -1})
}
}