2 ms·
IMMUTABLE also implies "does not change the database". http://www.postgresql.org/docs/9.2/static/sql-createfunction.html http://www.postgresql.org/docs/9.2/stat
by Someone 13y ago
IMMUTABLE also implies "does not change the database". http://www.postgresql.org/docs/9.2/static/sql-createfunction.html http://www.postgresql.org/docs/9.2/static/sql-createfunction...:
IMMUTABLE indicates that the function cannot modify the database and always returns the same result when given the same argument values; that is, it does not do database lookups or otherwise use information not directly present in its argument list. If this option is given, any call of the function with all-constant arguments can be immediately replaced with the function value.
STRICT does not mean 'no side effects'; it means 'returns NULL when given a NULL argument'. From the same page:
CALLED ON NULL INPUT (the default) indicates that the function will be called normally when some of its arguments are null. It is then the function author's responsibility to check for null values if necessary and respond appropriately.
RETURNS NULL ON NULL INPUT or STRICT indicates that the function always returns null whenever any of its arguments are null. If this parameter is specified, the function is not executed when there are null arguments; instead a null result is assumed automatically.
[looked that up because I couldn't think of a function that was STRICT but not IMMUTABLE according to the definition given]