silverstripe-sqlite3/README.md

67 lines
2.2 KiB
Markdown
Raw Normal View History

2010-01-14 21:42:43 +01:00
SQLite3 Module
==============
2014-02-18 05:59:32 +01:00
[![Build Status](https://travis-ci.org/silverstripe-labs/silverstripe-sqlite3.png?branch=master)](https://travis-ci.org/silverstripe-labs/silverstripe-sqlite3)
2010-01-14 21:42:43 +01:00
Maintainer Contact
------------------
Andreas Piening (Nickname: apiening)
<andreas (at) silverstripe (dot) com>
Requirements
------------
2012-07-06 15:57:01 +02:00
SilverStripe 3.0 or newer
2010-01-14 21:42:43 +01:00
Installation
------------
2013-03-15 09:50:53 +01:00
Download, unzip and copy the sqlite3 folder to your project root so that it becomes a sibling of `framework/`.
2013-03-15 09:50:53 +01:00
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)
2010-01-14 21:42:43 +01:00
$databaseConfig['type'] = 'SQLiteDatabase';
2013-04-01 20:24:29 +02:00
$databaseConfig['path'] = "/path/to/my/database/file";
2010-01-14 21:42:43 +01:00
2013-03-15 09:50:53 +01:00
Make sure the webserver has sufficient privileges to write to that folder and that it is protected from external access.
2010-01-14 21:42:43 +01:00
2011-01-17 01:14:30 +01:00
Sample mysite/_config.php
-------------------------
<?php
global $project;
$project = 'mysite';
global $database;
$database = 'SS_mysite';
require_once("conf/ConfigureFromEnv.php");
global $databaseConfig;
$databaseConfig = array(
"type" => 'SQLiteDatabase',
"server" => 'none',
"username" => 'none',
"password" => 'none',
"database" => $database,
"path" => "/path/to/my/database/file",
);
SSViewer::set_theme('blackcandy');
SiteTree::enable_nested_urls();
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
-------------
2011-01-17 01:14:30 +01:00
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
2010-01-14 21:42:43 +01:00
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 ;(
2010-01-14 21:42:43 +01:00
- there is no real fulltext search yet and the build-in search engine is not ordering by relevance, check out fts3