tonyair/silverstripe-postgresql
1
0
Fork 0
mirror of https://github.com/silverstripe/silverstripe-postgresql synced 2024-09-23 09:56:18 +02:00
Code Issues Projects Releases Wiki Activity
147 Commits 7 Branches 21 Tags 571 KiB
PHP 100%
b148e2457c
Go to file
James Pluck b148e2457c FIX Total Items count on Search 
This issue causes pagination to fail for search results on sites
using the postgres db.

Patch corrects the TotalItems in the returned List to show all items
matching the search criteria rather than just the items returned in
the current 'page' requested.
2014-08-01 15:33:58 +12:00
code FIX Total Items count on Search 2014-08-01 15:33:58 +12:00
docs MINOR: update Postgres doc for docviewer support. FIXES: #6681 2012-06-29 17:56:38 +12: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
.travis.yml Don't test against unsupported core versions 2014-07-11 09:26:11 +10:00
CHANGELOG MINOR: changelog for the 0.9.2 release 2010-11-11 20:50:57 +00:00
composer.json Create 1.1 branch for pre-3.2 support 2014-07-09 19:26:27 +10:00
LICENSE MINOR: Documentation update for the 0.9.1 release 2010-06-01 01:31:33 +00:00
README.md Added travis support 2014-02-18 17:56:10 +13: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. 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.