Go to file
NightjarNZ 0fa6b0fde7 FIX transaction depth related errors with invalid savepoint names
The logic for cancelling a savepoint was incorrect, as the behaviour
the logic was modelled on was for a different RDBMS - where a COMMIT
would always close the most recently opened transaction.

SQLite on contrast will commit the entire transaction, not just the
most recent savepoint marker until current execution point. The correct
manner to deal with a 'partial' commit is to call RELEASE <savepoint>.

This revealed an error in the savepoint logic, in that if someone had
supplied a savepoint name instead of relying on generated ones, the
rollback command did not factor for this and always assumed generated
savepoint names - again causing error. For this reason a new class
member field has been introduced to track savepoint names in a stack
fashion.
2018-10-11 22:07:23 +13:00
_config Upgrade for silverstripe namespaces 2016-09-08 15:41:17 +12:00
code FIX transaction depth related errors with invalid savepoint names 2018-10-11 22:07:23 +13:00
_config.php Upgrade for silverstripe namespaces 2016-09-08 15:41:17 +12:00
_configure_database.php Update config / code styles for 4.0 2017-11-23 14:11:10 +13:00
_register_database.php Update config / code styles for 4.0 2017-11-23 14:11:10 +13:00
.editorconfig Added standard .editorconfig file 2015-12-17 10:06:47 +13:00
.gitattributes Added standard .gitattributes file 2016-01-16 19:32:49 +13:00
.scrutinizer.yml Added standard Scrutinizer config 2016-03-23 23:18:23 +13:00
.travis.yml Update config / code styles for 4.0 2017-11-23 14:11:10 +13:00
.upgrade.yml API Apply SilverStripe\SQLite namespace to module 2016-06-29 13:55:45 +12:00
code-of-conduct.md Added standard code of conduct file 2016-02-16 11:42:22 +13:00
composer.json Update 2 branch alias to 2.2 2017-11-28 10:50:04 +13:00
LICENSE Create LICENSE 2013-09-02 21:20:35 +12:00
phpcs.xml.dist Update config / code styles for 4.0 2017-11-23 14:11:10 +13:00
phpunit.xml.dist Travis setup 2017-10-10 15:10:30 +01:00
README.md Add supported module badge to readme 2018-06-15 17:49:06 +12:00

SQLite3 Module

Build Status SilverStripe supported module

Maintainer Contact

Andreas Piening (Nickname: apiening) <andreas (at) silverstripe (dot) com>

Requirements

  • SilverStripe 4.0 or newer

Installation

  • Install using composer with composer require silverstripe/sqlite3 ^2.

Configuration

Either use the installer to automatically install SQLite or add this to your _config.php (right after "require_once("conf/ConfigureFromEnv.php");" if you are using _ss_environment.php)

$databaseConfig['type'] = 'SQLite3Database';
$databaseConfig['path'] = "/path/to/my/database/file";

Make sure the webserver has sufficient privileges to write to that folder and that it is protected from external access.

Sample mysite/_config.php

<?php
global $project;
$project = 'mysite';

global $database;
$database = 'SS_mysite';

require_once("conf/ConfigureFromEnv.php");

global $databaseConfig;
$databaseConfig = array(
	"type" => 'SQLite3Database',
	"server" => 'none',
	"username" => 'none',
	"password" => 'none',
	"database" => $database,
	"path" => "/path/to/my/database/file",
);

Again: make sure that the webserver has permission to read and write to the above path (/path/to/my/database/, 'file' would be the name of the sqlite db file)

URL parameter

If you're trying to change a field constrain to NOT NULL on a field that contains NULLs dev/build fails because it might corrupt existing records. In order to perform the action anyway add the URL parameter 'avoidConflict' when running dev/build which temporarily adds a conflict clause to the field spec. E.g.: http://www.my-project.com/?avoidConflict=1

Open Issues

  • SQLite3 is supposed to work with all may not work with certain modules as they are using custom SQL statements passed to the DB class directly ;(
  • there is no real fulltext search yet and the build-in search engine is not ordering by relevance, check out fts3