Go to file
Ingo Schommer 132c31bc80 Testing in PHP7
Now that we have support for PHP7 in SS 3.x, we should test the Postgres module against it.
I've set up the tests to run weekly on this branch (and master) via TravisCI new cron job feature.
While we have a nightly "all modules" run in silverstripe-installer, it doesn't have the same matrix coverage as this run here.

I've also removed removed tests against older (and unsupported) 3.x releases (it was testing against 3.2)
2017-06-27 15:58:40 +12:00
_config NEW: Allow 'null' limit in database queries 2015-05-04 15:36:49 +01:00
code BUG Fix decimal not supporting non-integer values 2015-11-03 09:14:10 +13:00
docs API Upgraded module to use new database ORM 2014-07-11 09:13:52 +12:00
tests Update API for 3.2 release 2015-06-17 13:50:36 +12:00
_config.php API Upgraded module to use new database ORM 2014-07-11 09:13:52 +12:00
_register_database.php API Upgraded module to use new database ORM 2014-07-11 09:13:52 +12:00
.editorconfig Adding .editorconfig 2015-01-03 17:19:27 +00:00
.travis.yml Testing in PHP7 2017-06-27 15:58:40 +12:00
CHANGELOG MINOR: changelog for the 0.9.2 release 2010-11-11 20:50:57 +00:00
composer.json Restrict 1.2 branch to 3.2 compatibility 2015-10-16 11:25:35 +13:00
LICENSE MINOR: Documentation update for the 0.9.1 release 2010-06-01 01:31:33 +00:00
README.md Alias dev-master as 1.2 2014-07-11 09:35:34 +12:00

PostgreSQL Module Module

Build Status

Maintainer Contact

Requirements

  • SilverStripe 3.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 1.2.*-dev 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.