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

MINOR: Documentation update for the 0.9.1 release

Browse Source
This commit is contained in:
Geoff Munn 2010-06-01 01:31:33 +00:00
parent 0c8580f3d7
commit 0d090e971f
3 changed files with 10 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
CHANGELOG
View File

@ -1,3 +1,10 @@
0.9.1
Released June 1st 2010
Changes:
Released for SilverStripe 2.4
This release coincides with the release of SilverStripe 2.4, where nearly all of the supported modules' tests pass
using this Postgres module
0.9.0
Released December 4 2009
Initial release of the PostgreSQL module

2
LICENSE
View File

@ -1,4 +1,4 @@
* Copyright (c) 2009, Silverstripe Ltd.
* Copyright (c) 2010, Silverstripe Ltd.
* All rights reserved.
*
* Redistribution and use in source and binary forms, with or without

9
README
View File

@ -11,7 +11,7 @@ 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 probably Linux
- Known to work on OS X Leopard, Windows Server 2008 R2 and Linux
Documentation
-----------------------------------------------
@ -32,16 +32,11 @@ See the documentation link for examples of PostgreSQL-specific functionality.
Known issues:
-----------------------------------------------
When you're setting this up for the first time, you will need to manually create the database 'SS_project' or whatever it's called.
I haven't implemented the automatic database creation logic yet.
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.
Most other modules probably don't work. There are many instances of MySQL-compatible backticks '`' littering existing modules,
and these need to be changed to double-quotes.
There may also be instances of MySQL-specific SQL queries which will need to be made database-agnostic where possible.
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.