-
-
Notifications
You must be signed in to change notification settings - Fork 3.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Breaking change since v1.24.4: Custom serializer on nil-slices #6306
Comments
The "workaround" for this (to support in go.mod:
|
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 |
This is related to the postgres-driver, see jackc/pgx#1566 for more infomation. |
This issue has been automatically marked as stale because it has been open 360 days with no activity. Remove stale label or comment or this will be closed in 180 days |
This fixes go-gorm/gorm#6306
I already reported this at go-gorm/postgres#159 a while ago, but it was ignored until now, probably because it's an issue in gorm itself. Since it's turning more and more into an issue for me, I decided to report it here as well:
go (simplified):
Before 1.4.6, my serializers converted nil-slices to empty json-arrays (
[]
string).Now, they are ignored, nil gets converted into a PostgreSQL null, and my not-null-constraints are triggered.
This prevents me from updating the gorm-dependency.
The text was updated successfully, but these errors were encountered: