v5:database:mysql
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revision | |||
v5:database:mysql [2023/05/10 09:41] – [mysqli driver] mysqlnd required since 5.22 dregad | v5:database:mysql [2024/04/30 13:07] (current) – Forcing emulated prepared statements dregad | ||
---|---|---|---|
Line 60: | Line 60: | ||
* Enable ADOdb | * Enable ADOdb | ||
*/ | */ | ||
- | $db = newAdoConnection(' | + | $db = newAdoConnection(' |
/* | /* | ||
* Set the SSL parameters | * Set the SSL parameters | ||
Line 81: | Line 81: | ||
* Enable ADOdb | * Enable ADOdb | ||
*/ | */ | ||
- | $db = newAdoConnection(' | + | $db = newAdoConnection(' |
$database = ' | $database = ' | ||
Line 94: | Line 94: | ||
*/ | */ | ||
$db-> | $db-> | ||
+ | </ | ||
+ | |||
+ | ==== Forcing emulated prepared statements ==== | ||
+ | |||
+ | ADOdb 5.22 introduced support for " | ||
+ | [[https:// | ||
+ | see [[https:// | ||
+ | Before that, parameterized queries were emulated, which was a potential security risk. | ||
+ | |||
+ | When using database engines pretending to be MySQL but not implementing prepared statements such as | ||
+ | [[https:// | ||
+ | [[https:// | ||
+ | it is possible((starting with ADOdb 5.22.8)) to force usage of emulated queries (i.e. reverting to behavior of ADOdb 5.21 and older) by setting the '' | ||
+ | |||
+ | <code php> | ||
+ | $db = newAdoConnection(' | ||
+ | $db-> | ||
+ | $db-> | ||
+ | $db-> | ||
</ | </ | ||
{{tag> | {{tag> | ||
{{htmlmetatags> | {{htmlmetatags> | ||
+ |
v5/database/mysql.1683704516.txt.gz · Last modified: 2023/05/10 09:41 by dregad