Welcome, Guest
Submit ComicRack bugs to get them squashed

TOPIC: [Shared database] unicode suport on DB fields

[Shared database] unicode suport on DB fields 2 years 10 months ago #41392

  • Fog
  • Fog's Avatar
  • Offline
  • Fresh Boarder
  • Posts: 5
  • Karma: 0
I tried to convert my xml DB into a database DB on MSSQL2012 but had to revert back because filenames with unicode chars were lost in the conversion to the DB...

For example a filename with japanese chars would be converted to ????.zip instead of the real filename
ファイル.zip which causes ComicRack to "think" that the file is missing.

I looked to the tables created and saw that the field type was TEXT instead of NTEXT to be able to support unicode chars.

Also on a small note...
TEXT / NTEXT will be removed from MSSQL in future versions, they're suggesting the use of VARCHAR(MAX) / NVARCHAR(MAX) unless you plan to support SQL2000 which is ancient :P

Heres the link from MS: msdn.microsoft.com/en-us/library/ms187993%28v=sql.90%29.aspx


Using:
ComicRack v0.9.176 64bit
MSSQL Server 2012
Windows 7 Ultimate 64bit
Last Edit: 2 years 10 months ago by Fog.
The administrator has disabled public write access.

[Shared database] unicode suport on DB fields 2 years 10 months ago #41406

  • laxarus
  • laxarus's Avatar
  • Offline
  • Senior Boarder
  • Posts: 66
  • Thank you received: 3
  • Karma: 0
You can try to use mysql instead of mssql. I have no problem with weird filenames using mysql.
The administrator has disabled public write access.
Time to create page: 0.154 seconds

Who's Online

We have 231 guests and 5 members online