fix(create): fix insert column order

[archever]

• Do only one thing
• Non breaking API changes
• Tested

What did this pull request do?

make insert sql column order stable for unittest

User Case Description

gorm create() interface generated sql not stable for each test run. I changed the map interater to a stable slice in order to keep the column order.

[a631807682]

Can you add some unit tests to describe what is being fixed?

[archever]

Can you add some unit tests to describe what is being fixed?

add a ut case

[a631807682]

The order of defaultValueFieldsHavingValue elements is based on FieldsWithDefaultDBValue. https://github.com/go-gorm/gorm/pull/6855/files#diff-7539aa7c170a85138fa67c7846b65fda95a51169bcf8637d5961ea570307d755R284
I don't understand why the order needs to be maintained here again, and the unit test passed before the change, can you describe why we need it?

[archever]

the type of defaultValueFieldsHavingValue is a map. before the change, column values is appended by iterating a map, which is not in a stable order. after the change, column values is appended following the order of FieldsWithDefaultDBValue, which is in stable order.

[jinzhu]

Hi @archever,

Thank you for your PR. Could you please remove those dependencies in go.mod? We aim to keep GORM's dependencies clean and tidy.

	github.com/stretchr/testify v1.8.4
)

require (
	github.com/davecgh/go-spew v1.1.1 // indirect
	github.com/pmezard/go-difflib v1.0.0 // indirect
	gopkg.in/yaml.v3 v3.0.1 // indirect
)

[archever]

@jinzhu done

[demoManito]

use t.Fatalf