.Indexes output should be consistent #82
Comments
Etomyutikos
pushed a commit
to codercom/gnorm
that referenced
this issue
Nov 28, 2017
fixes gnormal#82 The databases return index data in a consistent order. The previous process did not respect that through its use of a map as an intermediate store. By using slices, we now guarantee that the template will see the indexes in the order the database returned them.
natefinch
pushed a commit
that referenced
this issue
Dec 13, 2017
* ensure consistent index ordering fixes #82 The databases return index data in a consistent order. The previous process did not respect that through its use of a map as an intermediate store. By using slices, we now guarantee that the template will see the indexes in the order the database returned them. * pluralize tableIndex
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The
.Indexesfield on theTablestruct in the templates has an inconsistent order. This is due, most likely, to using a map instead of a slice indatabase/drivers/*/parse.go. The database returns the rows in a consistent order.It will also prevent regeneration of files from triggering diffs if there's no actual change in the data.
The text was updated successfully, but these errors were encountered: