summaryrefslogtreecommitdiff
path: root/doc/src
diff options
context:
space:
mode:
authorAndres Freund <andres@anarazel.de>2015-02-21 22:25:49 +0100
committerAndres Freund <andres@anarazel.de>2015-02-21 22:31:54 +0100
commiteb68379c38202180bc8e33fb9987284e314b7fc8 (patch)
tree0e6dcc59b1fabfe9c63b0d0377607acee7dad025 /doc/src
parent0627eff3602c0ce0e8358d48ddb3ffa73963e4d0 (diff)
Allow forcing nullness of columns during bootstrap.
Bootstrap determines whether a column is null based on simple builtin rules. Those work surprisingly well, but nonetheless a few existing columns aren't set correctly. Additionally there is at least one patch sent to hackers where forcing the nullness of a column would be helpful. The boostrap format has gained FORCE [NOT] NULL for this, which will be emitted by genbki.pl when BKI_FORCE_(NOT_)?NULL is specified for a column in a catalog header. This patch doesn't change the marking of any existing columns. Discussion: 20150215170014.GE15326@awork2.anarazel.de
Diffstat (limited to 'doc/src')
-rw-r--r--doc/src/sgml/bki.sgml9
1 files changed, 6 insertions, 3 deletions
diff --git a/doc/src/sgml/bki.sgml b/doc/src/sgml/bki.sgml
index aaf500ad082..af6d8d1d2a9 100644
--- a/doc/src/sgml/bki.sgml
+++ b/doc/src/sgml/bki.sgml
@@ -75,9 +75,12 @@
<optional><literal>without_oids</></optional>
<optional><literal>rowtype_oid</> <replaceable>oid</></optional>
(<replaceable class="parameter">name1</replaceable> =
- <replaceable class="parameter">type1</replaceable> <optional>,
- <replaceable class="parameter">name2</replaceable> = <replaceable
- class="parameter">type2</replaceable>, ...</optional>)
+ <replaceable class="parameter">type1</replaceable>
+ <optional>FORCE NOT NULL | FORCE NULL </optional> <optional>,
+ <replaceable class="parameter">name2</replaceable> =
+ <replaceable class="parameter">type2</replaceable>
+ <optional>FORCE NOT NULL | FORCE NULL </optional>,
+ ...</optional>)
</term>
<listitem>