From 0d090e971f0cf5de08ea4c6b1a15128fae2deec7 Mon Sep 17 00:00:00 2001 From: Geoff Munn Date: Tue, 1 Jun 2010 01:31:33 +0000 Subject: [PATCH] MINOR: Documentation update for the 0.9.1 release --- CHANGELOG | 7 +++++++ LICENSE | 2 +- README | 9 ++------- 3 files changed, 10 insertions(+), 8 deletions(-) diff --git a/CHANGELOG b/CHANGELOG index 34811d8..14ccc01 100644 --- a/CHANGELOG +++ b/CHANGELOG @@ -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 \ No newline at end of file diff --git a/LICENSE b/LICENSE index fbdddd0..514f4dc 100644 --- a/LICENSE +++ b/LICENSE @@ -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 diff --git a/README b/README index 377e0de..f35fc7c 100644 --- a/README +++ b/README @@ -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.