tonyair/silverstripe-postgresql
1
0
Fork 0
mirror of https://github.com/silverstripe/silverstripe-postgresql synced 2024-10-22 17:05:45 +02:00
Code Issues Projects Releases Wiki Activity
193 Commits 7 Branches 21 Tags 571 KiB
PHP 100%
1c953025e6
Go to file
Daniel Hensby 1c953025e6
Merge branch '1.1' into 1.2
2017-07-26 12:15:02 +01:00
_config NEW: Allow 'null' limit in database queries 2015-05-04 15:36:49 +01:00
code Merge branch '1.1' into 1.2 2017-07-26 12:15:02 +01: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 Merge branch '1.1' into 1.2 2017-07-26 12:15:02 +01:00
CHANGELOG MINOR: changelog for the 0.9.2 release 2010-11-11 20:50:57 +00:00
composer.json Merge branch '1.1' into 1.2 2017-07-26 12:15:02 +01: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

README.md

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.