[ http://issues.apache.org/jira/browse/DDLUTILS-108?page=comments#action_12413715 ]
Christoffer Hammarström commented on DDLUTILS-108: -------------------------------------------------- By the way, on the mailing list you said: "Most schemas that I have worked with, have used varchar instead of nvarchar and rather set the database language to a specific value. So, nvarchar would limit DdlUtils' usability even more. The only useful solution would be the introduction of the notion of fully supported unicode and non-unicode modes in DdlUtils." I don't understand how always using N*-types would limit the usability of DdlUtils, given that an N*-type can store everything a non-N*-type can, only using double the space? Going a bit anecdotal, i myself prefer to always use (say) NVARCHAR over VARCHAR, as i don't need to worry about the database not being able to store certain characters. Are there any other arguments against always using NCHAR/NVARCHAR/NTEXT instead of their non N-variants? > Unicode text fields (NTEXT, NVARCHAR, and NCHAR) for MSSQL > ---------------------------------------------------------- > > Key: DDLUTILS-108 > URL: http://issues.apache.org/jira/browse/DDLUTILS-108 > Project: DdlUtils > Type: Improvement > Components: Core > Environment: Microsoft SQL Server > Reporter: Christoffer Hammarström > Assignee: Thomas Dudziak > > I need to be able to store (for example) the contents of > http://www.cl.cam.ac.uk/~mgk25/ucs/examples/UTF-8-demo.txt in an NTEXT field > in an SQL Server database generated with ddlutils. > I'll try to make a patch. > Hibernate does it using another "dialect", which is analogous to a ddlutils > "platform", if i understand correctly: > http://confluence.atlassian.com/display/DOC/MSSQL+Tips#MSSQLTips-MSSQLandUnicode. > I'm thinking of two possibilites: either a new platform like hibernate called > something like "unicodemssql" (?), or some way to send a parameter into the > MSSqlPlatform or MSSqlBuilder. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
