I started my SQLite + Drupal development on yesterday, and now I have some good news: able to complete Drupal 6.x installer (hacked with Siren), face the welcome screen, install all optional module (except forum and search), generate dummy content with devel, and finally pass a AB stress test together with MySQL/PostgreSQL/Oracle. Since I work this out within my personal research project, I would like to give a comparison with ordinary Drupal 6.x CVS HEAD, too.
THE MOST IMPORTANT PROGRESS IS: the shared common code base based on my proposed personal battle targets for D7 is really effective. As mentioned above, I just spend 2 DAYS for this development, including the study of official SQLite documentation and existing D6 research progress. I didn't change any line of existing (hacked) core queries, especially for SQLite, after the successful development for MySQL/PostgreSQL/Oracle within Siren.
BTW, I did some trade-off within this implementation. Since it is just a research project, I am not going to work it as perfect but only functioning:
- I skip
sqlitebut dig intopdo_sqlitedirectly.This is because the functionality of SQLite is directly related to its libraries version; on the other hand,
pdo_sqliteis the official SQLite v3 PHP driver. At least SQLite v3.x come with RANDOM(), I would like to skipsqlitewith legacy SQLite v2.x supporting.Well... this is just a clone of existing pdo_pgsql research progress...
- The SQLite DB is now hardcoded in
/var/lib/drupal.This is because parse_url() don't always provide decoded $db_url as we expected (w/o leading
/will always result with unstable response). Since we may move to array syntax in D7, I skip the solution right now ;p - I skip ALL upgrade abstraction implementation.
The reason is version simple: SQLite don't really support ALTER TABLE and ALTER COLUMN as like as other database, most of the functionality are missed out. We may need Schema API's help for an elegant implementation, but that is not my primary research target.


















Post new comment