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
By default "id" field is generated as string type, which matches Mongo id type (mostly, as there's more issues with type of mongo id). However Mongo is planned to be dropped in version 4, and as I just found out, "id" field type on Postgres (and pretty surely all relational) is number. Which causes issues, I got around them by adding this to config
By default "id" field is generated as string type, which matches Mongo id type (mostly, as there's more issues with type of mongo id). However Mongo is planned to be dropped in version 4, and as I just found out, "id" field type on Postgres (and pretty surely all relational) is number. Which causes issues, I got around them by adding this to config
But I think it would be nicer if this is default behavior, and/or have a separate option for controlling type of "id" field.
The text was updated successfully, but these errors were encountered: