cartodb4/cartodb-postgresql
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Update CONTRIBUTING with information about function labels

Browse Source
This commit is contained in:
Raul Marin
2017-11-13 09:35:20 +01:00
committed by Raúl Marín
parent 9d980ab17c
commit 36550440bf
1 changed files with 7 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
CONTRIBUTING.md
+7 -1
View File
@@ -22,13 +22,19 @@ and upgrade of the objects. This means using CREATE OR REPLACE for
the functions, and whatever it takes to check existence of any previous the functions, and whatever it takes to check existence of any previous
version of objects in other cases. version of objects in other cases.
When adding a new function or modifying an exiting one make sure that the
[VOLATILITY](https://www.postgresql.org/docs/current/static/xfunc-volatility.html) and [PARALLEL](https://www.postgresql.org/docs/9.6/static/parallel-safety.html) categories are updated accordingly.
As PARALLEL labels need to be stripped for incompatible PostgreSQL versions
please use _PARALLEL SAFE/RESTRICTED/UNSAFE_ in uppercase so it's handled
automatically.
When used as an extension (probably always from version 0.2.0 onwards) When used as an extension (probably always from version 0.2.0 onwards)
all the objects will be installed in a "cartodb" schema. Take this into all the objects will be installed in a "cartodb" schema. Take this into
account to fully-qualify internal calls to avoid (possibly dangerous) account to fully-qualify internal calls to avoid (possibly dangerous)
name clashes. name clashes.
Every new feature (as well as bugfixes) should come with a test case, Every new feature (as well as bugfixes) should come with a test case,
see next section. see the 'Writing testcases' section.
Writing testcases Writing testcases
----------------- -----------------