mirrors/postgres
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

No longer need to cast default non-cacheable functions.

Browse Source
This commit is contained in:
Bruce Momjian 2000-04-13 07:19:27 +00:00
parent 97580f6993
commit 5eaa271b77
1 changed files with 1 additions and 16 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

17
doc/src/sgml/ref/create_table.sgml
View File

@ -1,5 +1,5 @@
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/ref/create_table.sgml,v 1.21 2000/04/12 04:40:03 thomas Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/ref/create_table.sgml,v 1.22 2000/04/13 07:19:27 momjian Exp $
Postgres documentation Postgres documentation
--> -->
@ -393,21 +393,6 @@ DEFAULT <replaceable class="PARAMETER">value</replaceable>
</variablelist> </variablelist>
</para> </para>
<para>
In the current release (v7.0), <productname>Postgres</productname>
evaluates all default expressions at the time the table is defined.
Hence, functions which are "non-cacheable" such as
<function>CURRENT_TIMESTAMP</function> may not produce the desired
effect. For the particular case of date/time types, one can work
around this behavior by using
<quote>DEFAULT TEXT 'now'</quote>
instead of
<quote>DEFAULT 'now'</quote>
or
<quote>DEFAULT CURRENT_TIMESTAMP</quote>.
This forces <productname>Postgres</productname> to consider the constant a string
type and then to convert the value to <type>timestamp</type> at runtime.
</para>
</refsect2> </refsect2>
<refsect2 id="R2-SQL-DEFAULTCLAUSE-4"> <refsect2 id="R2-SQL-DEFAULTCLAUSE-4">
<title> <title>