Open moolitayer opened 1 year ago
@jinzhu PTAL, I haven't been able to get to the root cause of this issue. Does this report make sense? Is there a way as a user of GORM to overcome the bug?
I have encountered the same issue, and each time it requires a conversion from character varying to varchar(32).
GORM Playground Link
https://github.com/go-gorm/playground/pull/646
Description
Every time we run AutoMigrage we get re-migration for certain specification of types:
A workaround is to specify the types in a different way (see reproduction) but the required types seems sphoradic. Not sure why, but the issue did not force migration before we upgraded GORM and the Postgres driver.
See the attached reproduction for details.