Commit71ff6c1

committed

Clarify CREATE FUNCTION documentation about handling of typmods.

The previous text was a bit misleading, as well as unnecessarily vagueabout what information would be discarded. Per gripe from Craig Skinner.

1 parent29bbca4 commit71ff6c1Copy full SHA for 71ff6c1

File tree

-6

lines changed

-6

lines changed

Lines changed: 7 additions & 6 deletions

Original file line number	Diff line number	Diff line change
`@@ -557,12 +557,13 @@ CREATE FUNCTION foo(int, int default 42) ...`
`557`	`557`
`558`	`558`	`<para>`
`559`	`559`	`The full <acronym>SQL</acronym> type syntax is allowed for`
`560`		`- input arguments and return value. However, some details of the`
`561`		`- type specification (e.g., the precision field for`
`562`		`- type <type>numeric</type>) are the responsibility of the`
`563`		`- underlying function implementation and are silently swallowed`
`564`		`- (i.e., not recognized or`
`565`		`- enforced) by the <command>CREATE FUNCTION</command> command.`
	`560`	`+ declaring a function's arguments and return value. However,`
	`561`	`+ parenthesized type modifiers (e.g., the precision field for`
	`562`	`+ type <type>numeric</type>) are discarded by <command>CREATE FUNCTION</>.`
	`563`	`+ Thus for example`
	`564`	`+ <literal>CREATE FUNCTION foo (varchar(10)) ...</>`
	`565`	`+ is exactly the same as`
	`566`	`+ <literal>CREATE FUNCTION foo (varchar) ...</>.`
`566`	`567`	`</para>`
`567`	`568`
`568`	`569`	`<para>`

Comments

(0)