Uploaded image for project: 'Confluence Data Center'
  1. Confluence Data Center
  2. CONFSERVER-2459

Need to use NVARCHAR columns in SQL Server to support Unicode

XMLWordPrintable

      MS SQL server won't let us put Unicode in the database with regular VARCHAR columns, it needs to use NVARCHAR instead.

      Evil, evil SQL Server.

            [CONFSERVER-2459] Need to use NVARCHAR columns in SQL Server to support Unicode

            Matt Ryall added a comment -

            New installations get NVARCHAR columns by default in 3.5. Verified on SQL Server Express Edition 2008.

            We didn't actually do anything to fix it in the 3.5 release, so it has probably been fixed for at least a couple of major versions before that.

            Matt Ryall added a comment - New installations get NVARCHAR columns by default in 3.5. Verified on SQL Server Express Edition 2008. We didn't actually do anything to fix it in the 3.5 release, so it has probably been fixed for at least a couple of major versions before that.

            Andrew Lynch (Inactive) added a comment -

            I think Oracle has the same behaviour.

            Andrew Lynch (Inactive) added a comment - I think Oracle has the same behaviour.

            Per Fragemann [Atlassian] added a comment -

            changed affects-29 to affects-28 to keep list of 2.9 bugs consistent

            Per Fragemann [Atlassian] added a comment - changed affects-29 to affects-28 to keep list of 2.9 bugs consistent

            Paul Curren added a comment - - edited

            Testing of Confluence 2.9 on SQL Server 2005 with Latin1_General_CI_AS collation obviously still has the same problem. Pretty annoying.

            Paul Curren added a comment - - edited Testing of Confluence 2.9 on SQL Server 2005 with Latin1_General_CI_AS collation obviously still has the same problem. Pretty annoying.

            Charles Miller (Inactive) added a comment -

            We need to find a way to fix this issue. It's pretty annoying for anyone using SQL Server to either be SOL WRT high bit characters, or have to redo their mapping files every release.

            Pushing up the priority queue..

            Charles Miller (Inactive) added a comment - We need to find a way to fix this issue. It's pretty annoying for anyone using SQL Server to either be SOL WRT high bit characters, or have to redo their mapping files every release. Pushing up the priority queue..

              matt@atlassian.com Matt Ryall
              cmiller@atlassian.com Charles Miller (Inactive)
              Affected customers:
              5 This affects my team
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: