Łukasz Mierzwa b754155266 Store alert sha1 internally and use it as a secondary key when sorting ...

We already compute alert sha1, it's a unique string so it's a good match for secondary sort key, used when two alerts have the exact same
timestamp. This helps to ensure that we always have a stable sort order and don't flash the UI if we have a group with alerts created at the exact same time

2017-03-29 19:48:02 -07:00

..

models_test.go

Store alert sha1 internally and use it as a secondary key when sorting

2017-03-29 19:48:02 -07:00

models.go

Store alert sha1 internally and use it as a secondary key when sorting

2017-03-29 19:48:02 -07:00