Rev 1365 | Rev 1370 | Go to most recent revision | Show entire file | Regard whitespace | Details | Blame | Last modification | View Log | RSS feed
| Rev 1365 | Rev 1368 | ||
|---|---|---|---|
| Line 22... | Line 22... | ||
| 22 | - [DONE] SQL Server needs nvarchar instead of varchar (works with emoji too) |
22 | - [DONE] SQL Server needs nvarchar instead of varchar (works with emoji too) |
| 23 | - [DONE] MySQL works with Unicode and emoji if collation is utf8mb4 |
23 | - [DONE] MySQL works with Unicode and emoji if collation is utf8mb4 |
| 24 | - [DONE] Access table structure works with Unicode |
24 | - [DONE] Access table structure works with Unicode |
| 25 | - PDO+MySQL: Unicode (with emoji) works, but PDO+ODBC+MSSQL and PDO+ODBC+ACCESS does not work, so it's ODBC's or ODBC-Driver's fault. Can we do something about it? |
25 | - PDO+MySQL: Unicode (with emoji) works, but PDO+ODBC+MSSQL and PDO+ODBC+ACCESS does not work, so it's ODBC's or ODBC-Driver's fault. Can we do something about it? |
| 26 | - ODBC+MSSQL and ODBC+ACCESS: Unicode does not work. So it's ODBC's or ODBC-Driver's fault. Can we do something about it? |
26 | - ODBC+MSSQL and ODBC+ACCESS: Unicode does not work. So it's ODBC's or ODBC-Driver's fault. Can we do something about it? |
| 27 | (Note: ODBC and PDO can save UTF-8, but then they are double-encoded in DBTool/Access/SQLManagementStudio. When you insert Unicode in DBTool/Access/SQLManagementStudio, then they show up as '??' in OIDplus) |
27 | (Note: OIDplus can read and write UTF-8 with ODBC and PDO and it looks good if you look at it in OIDplus. However, the data is actually double-encoded, which can be noticed if you view the data in SQL Management Studio, Access, or any other tool. When you insert Unicode in SQL Management Studio, then it shows up as '??' in OIDplus) |
| - | 28 | - The following trick might work (not tested) https://www.php.net/manual/en/function.odbc-connect.php#123797 , so that Unicode can work correctly with ODBC |
|
| 28 | - [DONE] ADO+OLEDB works with Unicode and emoji. It is important that the COM class is created with codepage 65001, and that SQL commands use N'...' strings |
29 | - [DONE] ADO+OLEDB works with Unicode and emoji. It is important that the COM class is created with codepage 65001, and that SQL commands use N'...' strings |
| 29 | - [DONE] SRVSRV plugin is capable of Unicode and pile of poo Emoji. |
30 | - [DONE] SRVSRV plugin is capable of Unicode and pile of poo Emoji. Tested reading and writing (Update commmand). |
| 30 | 31 | ||
| 31 | Exception Refactoring: |
32 | Exception Refactoring: |
| 32 | - [DONE] Instead of catching OIDplusException, catch Exception |
33 | - [DONE] Instead of catching OIDplusException, catch Exception |
| 33 | - [DONE] Check every "new OIDplusException" and "new \OIDplusException" if it contains HTML and needs to be "new OIDplusHtmlException" |
34 | - [DONE] Check every "new OIDplusException" and "new \OIDplusException" if it contains HTML and needs to be "new OIDplusHtmlException" |
| 34 | - [DONE] Check every instance of "->getMessage()" it it needs to be HTML or Text |
35 | - [DONE] Check every instance of "->getMessage()" it it needs to be HTML or Text |