Rev 1240 | Rev 1243 | Go to most recent revision | Show entire file | Regard whitespace | Details | Blame | Last modification | View Log | RSS feed
| Rev 1240 | Rev 1241 | ||
|---|---|---|---|
| Line 7... | Line 7... | ||
| 7 | * Everywhere where url_get_contents() is used, we need to check url_get_contents_available() too. |
7 | * Everywhere where url_get_contents() is used, we need to check url_get_contents_available() too. |
| 8 | - Not good: url_*_contents() throws an Exception if not available, but returns false if URL is not available. That's inconsistant... |
8 | - Not good: url_*_contents() throws an Exception if not available, but returns false if URL is not available. That's inconsistant... |
| 9 | - Idea: If we enter "oid:2.999.123" in the goto box, and only "oid:2.999" exists, should we recommend the user to look at 2.999? |
9 | - Idea: If we enter "oid:2.999.123" in the goto box, and only "oid:2.999" exists, should we recommend the user to look at 2.999? |
| 10 | - Idea: If someone enters an OID in the goto box, should we prepend "oid:" (but only if all other plugins rejected the request)? |
10 | - Idea: If someone enters an OID in the goto box, should we prepend "oid:" (but only if all other plugins rejected the request)? |
| 11 | - setup/sql/*.sql should be in plugins/*/sqlSlang/*.sql |
11 | - setup/sql/*.sql should be in plugins/*/sqlSlang/*.sql |
| 12 | - Finish implementing Firebird SQL slang |
- | |
| 13 | * Transactions via PDO not possible?! |
- | |
| 14 | 12 | ||
| 15 | Future: |
13 | Future: |
| 16 | - Check if we can also support these databases listed at the PHP documentation: |
14 | - Check if we can also support these databases listed at the PHP documentation: |
| 17 | CUBRID |
15 | CUBRID |
| 18 | dBase |
16 | dBase |
| 19 | Firebird/InterBase |
17 | Firebird/InterBase => No. This PHP extension is not maintained anymore |
| 20 | IBM DB2 IBM DB2, Cloudscape and Apache Derby |
18 | IBM DB2 IBM DB2, Cloudscape and Apache Derby |
| 21 | 19 | ||
| 22 | Unicode compatibility: |
20 | Unicode compatibility: |
| 23 | - [DONE] SQL Server needs nvarchar instead of varchar (works with emoji too) |
21 | - [DONE] SQL Server needs nvarchar instead of varchar (works with emoji too) |
| 24 | - [DONE] MySQL works with Unicode and emoji if collation is utf8mb4 |
22 | - [DONE] MySQL works with Unicode and emoji if collation is utf8mb4 |