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 ✨
i met the same issue when update gorm to v1.25.11, when I downgrade version to 1.25.10, issue was resolved. but it can not be reproduced again after upgrade back to v1.25.11
working fine with following version dependencies
gorm.io/driver/postgres v1.5.9
gorm.io/gen v0.3.26
gorm.io/gorm v1.25.11
gorm.io/plugin/dbresolver v1.5.0
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 ✨
Description
I use the "gen" to generate the code about accessing to the database.
But when execute the "gen", problem occurred:
construct "gorm.PreparedStmtDB" with field "PreparedSQL"
but in my version there's no field name "PreparedSQL" in "gorm.PreparedStmtDB"
here's my version number in trouble
gorm.io/gen v0.3.26
gorm.io/gorm v1.25.12
And after I change the gorm version into v1.25.9, problem solved.
The text was updated successfully, but these errors were encountered: