Order of createdAt, deletedAt and updatedAt have different order if schema.graphql is re-generated

[frederikhors]

I see some fields in the schema.graphql are written everytime in different order.

Example

1. First time:

input UserWhere {
  id: IDFilter
  email: StringFilter
  password: StringFilter
  updatedAt: IntFilter // this is here now
  createdAt: IntFilter
}

1. Second time:

input UserWhere {
  id: IDFilter
  email: StringFilter
  password: StringFilter
  createdAt: IntFilter
  updatedAt: IntFilter // this is here now
}

And so on...

This is a problem as you can imagine.

[RichardLindhout]

This is indeed a bug It's because the process interferes here and add the createdAt and updatedAt later https://github.com/web-ridge/gqlgen-sqlboiler/blob/main/sqlboiler.go#L241

But it does not work since golang maps are randomly sorted so this needs to change, I'm a little short on time at the moment maybe you could create a PR to fix this.

I think it would be fixed if instead of 1000000 + i we would do 100 * i

[RichardLindhout]

This should be fixed in development, will let you know when it is released

[RichardLindhout]

Should be fixed in 3.1.0