485
edits
Make your applications work in DataFlex NextGen: Difference between revisions
From DataFlex Wiki
Jump to navigationJump to search
Make your applications work in DataFlex NextGen (view source)
Revision as of 13:31, 24 April 2021
, 24 April 2021Update to supported database types now that DF20 has been released
(Update to supported database types now that DF20 has been released) |
|||
| (One intermediate revision by the same user not shown) | |||
| Line 141: | Line 141: | ||
SQL is the preferred database type. | SQL is the preferred database type. | ||
MSSQL has unicode datatypes (he "n" variants) : nvarchar, nchar, nvarchar(max), ntext | MSSQL has unicode datatypes (he "n" variants) : nvarchar, nchar, nvarchar(max), ntext. those are all UTF-16. | ||
MSSQL 2019 will support UTF-8 | MSSQL 2019 will support UTF-8, this is not recommended (or supported) at this moment. | ||
MySQL supports both UTF-16 as well as UTF-8 | |||
DB2 supports UTF-8 and UTF-16 | |||
The embedded database only supports OEM and has no unicode support. | |||
The Connectivity kit handles all of the character translations between database backend and UTF-8 strings. | |||
== Migrating to Unicode == | == Migrating to Unicode == | ||
| Line 152: | Line 157: | ||
Bytes are not code points, one character can take up to 4 bytes. | Bytes are not code points, one character can take up to 4 bytes. | ||
== more info on unicode == | |||
* https://home.unicode.org/ (The unicode consortium official home page) | |||
* https://www.unicode.org/standard/WhatIsUnicode.html | |||
* [https://unicode-table.com/en/ unicode-table.com] | |||
* [https://apps.timwhitlock.info/unicode/inspect timwhitlock unicode inspect app] | |||
[[Category:How To]] | [[Category:How To]] | ||
[[Category:Tutorials]] | [[Category:Tutorials]] | ||
