Post History
The problem here is that you are conflating two separate things: the syntax for parameters in a function expression and the list of available parameters. The syntax itself is straightforward enough...
Answer
#4: Attribution notice removed
by
System
·
2020-01-03T20:41:54Z (over 4 years ago)
Source: https://writers.stackexchange.com/a/28989 License name: CC BY-SA 3.0 License URL: https://creativecommons.org/licenses/by-sa/3.0/
#3: Attribution notice added
by
System
·
2019-12-08T06:42:17Z (over 4 years ago)
Source: https://writers.stackexchange.com/a/28989 License name: CC BY-SA 3.0 License URL: https://creativecommons.org/licenses/by-sa/3.0/
#2: Initial revision
by
System
·
2019-12-08T06:42:17Z (over 4 years ago)
The problem here is that you are conflating two separate things: the syntax for parameters in a function expression and the list of available parameters. The syntax itself is straightforward enough:
CREATE PARSER [schema.]function
[WITH [parameter='value' [, parameter='value']+]
];
The list of parameters is:
LANGUAGE='language'
MODE='[FENCED | UNFENCED]'
STUFF='anotherParameter'
Most API documentation separates these two things, which would seem to solve your problem.
BTW, you might point out to your developers that since the parameter values are quoted, the comma is syntactically redundant. Removing it would simplify your diagram and even let you continue to conflate parameter syntax with the list of parameters if you really wanted to.
#1: Imported from external source
by
System
·
2017-06-29T09:57:39Z (almost 7 years ago)
Original score: 3