You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The issue has been automatically marked as stale as it missing playground pull request link, which is important to help others understand your issue effectively and make sure the issue hasn't been fixed on latest master, checkout https://github.com/go-gorm/playground for details. it will be closed in 30 days if no further activity occurs. if you are asking question, please use the Question template, most likely your question already answered https://github.com/go-gorm/gorm/issues or described in the document https://gorm.io ✨ Search Before Asking ✨
Unfortunately it seems that the fix of this ticket is not perfectly fine, especially this part:
// check type
if !field.PrimaryKey && !strings.HasPrefix(fullDataType, realDataType) {
alterColumn = true
}
I was wondering why after updating gorm the auto migration was taking so long. I found that I was using type int32 (not null) in my models, which caused the issue. While debugging I found that in here for int32 and postgres dialect the fullDataType is integer not null and realDataType is int4 which is fine in general but due to the upper code snippet it runs a migration every time for all int32 fields.
@a631807682 is there any chance to limit this condition to the mentioned data types, as this might affect others as well.
GORM Playground Link
go-gorm/playground#1
Description
The text was updated successfully, but these errors were encountered: