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
But some culture names are much longer. The longest culture names are 11 characters:
en-US-POSIX
mni-Beng-IN
sat-Olck-IN
shi-Latn-MA
shi-Tfng-MA
tzm-Arab-MA
tzm-Tfng-MA
vai-Latn-LR
vai-Vaii-LR
They are very specific, but in our usecase we use cultures with length of 10 characters. So this is a real problem for us.
Now we get the following exception:
NHibernate.Exceptions.GenericADOException: 'could not execute batch command.[SQL: SQL not available]'
SqlException: String or binary data would be truncated in table ...
The text was updated successfully, but these errors were encountered:
The current generated SQL type for the
CultureInfo
object is string(5):nhibernate-core/src/NHibernate/Type/CultureInfoType.cs
Line 21 in 07c367f
But some culture names are much longer. The longest culture names are 11 characters:
en-US-POSIX
mni-Beng-IN
sat-Olck-IN
shi-Latn-MA
shi-Tfng-MA
tzm-Arab-MA
tzm-Tfng-MA
vai-Latn-LR
vai-Vaii-LR
They are very specific, but in our usecase we use cultures with length of 10 characters. So this is a real problem for us.
Now we get the following exception:
NHibernate.Exceptions.GenericADOException: 'could not execute batch command.[SQL: SQL not available]'
SqlException: String or binary data would be truncated in table ...
The text was updated successfully, but these errors were encountered: