tonyair/silverstripe-postgresql
1
0
Fork 0
mirror of https://github.com/silverstripe/silverstripe-postgresql synced 2024-10-22 15:05:45 +00:00
Code Issues Projects Releases Wiki Activity
117 Commits 7 Branches 21 Tags
Go to file
Clone
Open with VS Code Open with VSCodium Open with Intellij IDEA
Damian Mooyman 3291147c8e FIXED: Issue with correct extraction of index names from the database. The root cause of this issue was the way that columns from indxes were retrieved. It was assumed that the column names formed the index name, which isn't necessarily true (E.g. when the index is named "SearchFields"). The behaviour of the module was updated to create case-sensitive index and trigger names, which could then be used to later tell Silverstripe which indexes existed in the database. These could be compared to the SiteTree::$indexes property in a case-sensitive fashion to determine which indexes needed to be created / updated. This update fixes a lot of the unnecessary/broken DDL operations that occurred.
2012-09-17 16:15:00 +12:00
code
FIXED: Issue with correct extraction of index names from the database. The root cause of this issue was the way that columns from indxes were retrieved. It was assumed that the column names formed the index name, which isn't necessarily true (E.g. when the index is named "SearchFields"). The behaviour of the module was updated to create case-sensitive index and trigger names, which could then be used to later tell Silverstripe which indexes existed in the database. These could be compared to the SiteTree::$indexes property in a case-sensitive fashion to determine which indexes needed to be created / updated. This update fixes a lot of the unnecessary/broken DDL operations that occurred.
2012-09-17 16:15:00 +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
CHANGELOG
MINOR: changelog for the 0.9.2 release
2010-11-11 20:50:57 +00:00
LICENSE
MINOR: Documentation update for the 0.9.1 release
2010-06-01 01:31:33 +00:00
README.md
MINOR Updating installation instructions
2012-07-04 14:18:29 +12:00

README.md

PostgreSQL Module Module

Maintainer Contact

Requirements

  • SilverStripe 2.4
  • 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.

Description
No description provided
Readme 571 KiB
Languages
PHP 100%