Move in-place upgrade of functions from README to CONTRIBUTING

This commit is contained in:
Sandro Santilli
2014-06-17 10:43:49 +02:00
parent 44d32e4db5
commit 1815096a37
2 changed files with 26 additions and 16 deletions
+2 -16
View File
@@ -87,19 +87,5 @@ ls `pg_config --sharedir`/extension/cartodb*
```
During development the cartodb extension version doesn't change with
every commit, so testing latest change requires cheating with PostgreSQL
so to enforce re-load of the scripts. To help with cheating, "make install"
also installs migration scripts to go from "V" to "V"next and from "V"next
to "V". Example to upgrade a 0.2.0dev version:
```sql
ALTER EXTENSION cartodb UPDATE TO '0.2.0devnext';
ALTER EXTENSION cartodb UPDATE TO '0.2.0dev';
```
Starting with 0.2.0, the in-place reload can be done with an ad-hoc function:
```sql
SELECT cartodb.cdb_extension_reload();
```
every commit, so testing latest change requires special steps documented
in the CONTRIBUTING document, under "Testing changes live".