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
{{ message }}
This repository has been archived by the owner on Oct 8, 2024. It is now read-only.
Need to consider the use of NVARCHAR, rather than plain VARCHAR. For example, both the US and International Editions of the SNOMED CT clinical coding system contain terms that can only rendered correctly in Unicode.
The text was updated successfully, but these errors were encountered:
Good point...all text should be represented as unicode.
I'll plan on replacing all VARCHAR references with NVARCHAR to make this explicit, and databases can use that or an equivalent for those that don't directly support it.
Need to consider the use of NVARCHAR, rather than plain VARCHAR. For example, both the US and International Editions of the SNOMED CT clinical coding system contain terms that can only rendered correctly in Unicode.
The text was updated successfully, but these errors were encountered: