Go to file
2017-11-28 10:38:01 +13:00
_config FIX Quote yample starting with % 2017-07-27 10:41:34 +01:00
code BUG Fix postgres + PDO not working 2017-11-20 09:07:32 +13:00
docs API Upgraded module to use new database ORM 2014-07-11 09:13:52 +12:00
tests BUG Fix postgres + PDO not working 2017-11-20 09:07:32 +13:00
_register_database.php BUG Fix installer for 4.0 (#58) 2016-10-26 14:24:00 +13:00
.editorconfig BUG Fix postgres + PDO not working 2017-11-20 09:07:32 +13:00
.gitattributes Added standard .gitattributes file 2016-01-16 19:34:48 +13:00
.scrutinizer.yml BUG Fix postgres + PDO not working 2017-11-20 09:07:32 +13:00
.travis.yml Correcting travis install steps 2017-11-21 11:38:00 +00:00
.upgrade.yml Upgrade code for new namespaces 2016-07-04 13:32:41 +12:00
CHANGELOG MINOR: changelog for the 0.9.2 release 2010-11-11 20:50:57 +00:00
code-of-conduct.md Added standard code of conduct file 2016-02-16 11:43:48 +13:00
composer.json Merge branch '2' 2017-11-28 10:38:01 +13:00
LICENSE MINOR: Documentation update for the 0.9.1 release 2010-06-01 01:31:33 +00:00
phpcs.xml.dist BUG Fix postgres + PDO not working 2017-11-20 09:07:32 +13:00
phpunit.xml.dist BUG Fix postgres + PDO not working 2017-11-20 09:07:32 +13:00
README.md Remove version constraint 2017-11-21 18:32:56 +13:00

PostgreSQL Module Module

Build Status

Maintainer Contact

Requirements

  • SilverStripe 4.0
  • PostgreSQL 8.3.x or greater must be installed
  • PostgreSQL <8.3.0 may work if T-Search is manually installed
  • Known to work on OS X Leopard, Windows Server 2008 R2 and Linux

Installation

  1. Install via composer composer require silverstripe/postgresql or extract the contents so they reside as a postgresql directory inside your SilverStripe project code
  2. Open the installer by browsing to install.php, e.g. http://localhost/silverstripe/install.php
  3. Select PostgreSQL in the database list and enter your database details

Usage Overview

See docs/en for more information about configuring the module.

Known issues

All column and table names must be double-quoted. PostgreSQL automatically lower-cases columns, and your queries will fail if you don't.

Ts_vector columns are not automatically detected by the built-in search filters. That means if you're doing a search through the CMS on a ModelAdmin object, it will use LIKE queries which are very slow. If you're writing your own front-end search system, you can specify the columns to use for search purposes, and you get the full benefits of T-Search.

If you are using unsupported modules, there may be instances of MySQL-specific SQL queries which will need to be made database-agnostic where possible.