|
|
||
|---|---|---|
| _config | ||
| .github/workflows | ||
| code | ||
| docs | ||
| tests | ||
| _register_database.php | ||
| .editorconfig | ||
| .gitattributes | ||
| .upgrade.yml | ||
| CHANGELOG | ||
| code-of-conduct.md | ||
| composer.json | ||
| LICENSE | ||
| phpcs.xml.dist | ||
| phpunit.xml.dist | ||
| README.md | ||
PostgreSQL Module Module
Maintainer Contact
- Sam Minnee (Nickname: sminnee) sam@silverstripe.com
Requirements
- Silverstripe 4.0
- PostgreSQL >=9.2
- Note: PostgreSQL 10 has not been tested
Installation
composer require silverstripe/postgresql
Configuration
Environment file
Add the following settings to your .env file:
SS_DATABASE_CLASS=PostgreSQLDatabase
SS_DATABASE_USERNAME=
SS_DATABASE_PASSWORD=
See environment variables for more details. Note that a database will automatically be created via dev/build.
Through the installer
Open the installer by browsing to install.php, e.g. http://localhost/install.php 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.