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
SQL server needs to use the nvarchar() type to support unicode content. On a related note, nvarchar(max) is the current unicode-ready replacement for text.
However the default GORM Hibernate mappings, even when using the latest org.hibernate.dialect.SQLServer2016Dialect still use the non-unicode compatible varchar and text types.
You can work around this on a per-field basis, i.e. with this mapping for a Comment class where we want the body field to support arbitrarily long strings of unicode text:
But it would be great if we could include a Hibernate dialect within Hoist that a dev could specify to get unicode-by-default out of the box for string fields.
The text was updated successfully, but these errors were encountered:
SQL server needs to use the
nvarchar()
type to support unicode content. On a related note,nvarchar(max)
is the current unicode-ready replacement fortext
.However the default GORM Hibernate mappings, even when using the latest
org.hibernate.dialect.SQLServer2016Dialect
still use the non-unicode compatiblevarchar
andtext
types.You can work around this on a per-field basis, i.e. with this mapping for a
Comment
class where we want thebody
field to support arbitrarily long strings of unicode text:But it would be great if we could include a Hibernate dialect within Hoist that a dev could specify to get unicode-by-default out of the box for string fields.
The text was updated successfully, but these errors were encountered: