diff options
author | Tom Willemse | 2024-06-10 23:38:09 -0700 |
---|---|---|
committer | Tom Willemse | 2024-06-10 23:38:09 -0700 |
commit | eb81d7b851f51ab5919be78493737ef2abf49aab (patch) | |
tree | 8559f83f83e1cab0b6cb9a0d0fa94f8b0bcb1959 /includes/js/dojox/_sql | |
parent | c6101ba37422dcfcf16131d9dc41692e0725aa81 (diff) | |
download | scuttle-eb81d7b851f51ab5919be78493737ef2abf49aab.tar.gz scuttle-eb81d7b851f51ab5919be78493737ef2abf49aab.zip |
Fix using SQLite as a database engine
- The ‘sqlite_*’ functions don't exist anymore in PHP 8. They have been replaced
with several ‘SQLite3*’ classes.
- There are some differences between MySQL and SQLite queries that showed up
while doing this work. These differences have been pushed into a QueryBuilder
class so that the other database engines don't have to be modified. This is
done in an ad-hoc basis for now, just to get things working.
- SQLite doesn't support the ‘!’ negation operator used as ‘!ISNULL(...)’,
instead I use ‘IIF(...)’.
- SQLite doesn't support a ‘LEFT(...)’ function, instead I use ‘SUBSTRING(...,
0, ...)’.
- The SQLite3 module doesn't provide a connection identifier, instead you use an
object that represents the connection.
- SQLite doesn't support the ‘ALL’ keyword (or at least doesn't support it in
the same way MySQL does). Instead of ‘<> ALL <subquery>’ I use ‘NOT IN
<subquery>’.
- The ‘SQLite3*’ classes don't provide any way to determine how many rows have
been returned without iterating through all of them, so any place that tries
to figure out the rows beforehand just doesn't anymore.
- All the database engine classes require a ‘QueryBuilder’ instance. The sqlite
one uses a specialized one. I can't test most of these database engines, so
I'm focusing on SQLite and MySQL/MariaDB for now.
Diffstat (limited to 'includes/js/dojox/_sql')
0 files changed, 0 insertions, 0 deletions