Investigate if we can use the following type mappings for SQL Server Dialects

Description

I found a blog post which says that the following type mappings should be used for SQL Server:

We should investigate and see if they should be used by default.

Environment

None

Activity

Show:
Chris Cranford
March 21, 2017, 7:07 PM
Edited

I don't necessarily agree with the post's use of NVARCHAR for all VARCHAR / CLOB based data types. That would impose a massive performance decrease in general for all String columns. Users should opt-in for this use by either using @Nationalized or the config property hibernate.use_nationalized_character_data.

Other data types this blog post outlines were introduced as part of SQLServer2005Dialect. This may have been done due to an oversight on the original SQLServerDialect and rather than impose concerns with schema generation backward compatibility, we elected to maintain these as part of SQLServer2005Dialect going forward?

Vlad Mihalcea
March 22, 2017, 7:32 AM

Thanks, . I'm going to close this issue since you are right. We already cover most of these settings, and moving to NVarChar is not really a good default.

Assignee

Vlad Mihalcea

Reporter

Vlad Mihalcea

Fix versions

None

Labels

None

backPortable

None

Suitable for new contributors

None

Requires Release Note

None

Pull Request

None

backportDecision

None

Components

Affects versions

Priority

Major
Configure