Go to file
Ingo Schommer 618d7f1137 Less restrictive compatibility notation in composer
Support 2.5.x ("post-2.4") as well
2012-11-28 22:07:12 +01:00
code BUGFIX: Fixes #7123. Sets timezone of database if specified. 2012-04-16 11:49:35 +12:00
docs MINOR: Documentation now in markdown format 2011-01-18 17:31:28 +13:00
tests MINOR Added PostgreSQLDatabaseTest with a database specific readonly transaction test (moved here from sapphire/tests/TransactionTest.php 2011-03-14 16:47:44 +13:00
_config.php GiST and Tsvector references removed so DB/build will work 2009-01-09 03:43:28 +00:00
CHANGELOG MINOR: changelog for the 0.9.2 release 2010-11-11 20:50:57 +00:00
composer.json Less restrictive compatibility notation in composer 2012-11-28 22:07:12 +01:00
LICENSE MINOR: Documentation update for the 0.9.1 release 2010-06-01 01:31:33 +00:00
README MINOR: Documentation update for the 0.9.1 release 2010-06-01 01:31:33 +00:00

###############################################
PostgreSQL Module
###############################################

Maintainer Contact
-----------------------------------------------
Geoff Munn (Nickname: gmunn)
<geoff (at) silverstripe (dot) com>

Requirements
-----------------------------------------------
- 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

Documentation
-----------------------------------------------
http://doc.silverstripe.org/doku.php?id=postgres

Installation Instructions
-----------------------------------------------

Move the 'postgres' folder to the root level of the project.
You'll need to create a database with the desired name manually. 
Run dev/build and you should be set.

Usage Overview
-----------------------------------------------

See the documentation link for examples of PostgreSQL-specific functionality.

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.