| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Taken care of by loggingmanager now
|
|
|
|
|
|
| |
Tested with SQLite3 3.16.2 and 3.27.2 and Postgres 11.
MySQL does not support IF NOT EXISTS for indices so not handled here.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
(Thanks Ge0rG)
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
encoding checks in mod_storage_sql (thanks Martin)
|
|
|
|
| |
accents for MySQL only (fixes #885)
|
| |
|
| |
|
| |
|
|
|
|
| |
only error message (fixes #464)
|
|
|
|
| |
charset_ok to true), fixes bug introduced in 187ba2e9c012
|
| |
|
| |
|
| |
|
|
|
|
| |
its own method
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
return them in a table at the end
|
| |
|
|
|
|
| |
actually being used (MySQL)
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
MySQL silently ignoring our SET NAMES command when we use utf8mb4
|
|
|
|
| |
connection, also use corresponding _bin collation
|
|
|
|
| |
false, err
|
| |
|
|
|
|
| |
this, and unintentionally sharing connections could cause problems (e.g. when interleaving multiple queries and result fetching)
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|