Commitfead794

committed

Docs: improve examples about not repeating table name in UPDATE ... SET.

Alexander Law

1 parent31ce32a commitfead794Copy full SHA for fead794

File tree

-3

lines changed

-3

lines changed

Lines changed: 2 additions & 2 deletions

Original file line number	Diff line number	Diff line change
`@@ -194,8 +194,8 @@ INSERT INTO <replaceable class="PARAMETER">table_name</replaceable> [ AS <replac`
`194`	`194`	`column leaves the other fields null.) When referencing a`
`195`	`195`	`column with <literal>ON CONFLICT DO UPDATE</>, do not include`
`196`	`196`	`the table's name in the specification of a target column. For`
`197`		`- example, <literal>INSERT ... ON CONFLICT DO UPDATE tab SET`
`198`		`- table_name.col = 1</> is invalid (this follows the general`
	`197`	`+ example, <literal>INSERTINTO table_name... ON CONFLICT DO UPDATE`
	`198`	`+SETtable_name.col = 1</> is invalid (this follows the general`
`199`	`199`	`behavior for <command>UPDATE</>).`
`200`	`200`	`</para>`
`201`	`201`	`</listitem>`

Lines changed: 1 addition & 1 deletion

Original file line number	Diff line number	Diff line change
`@@ -123,7 +123,7 @@ UPDATE [ ONLY ] <replaceable class="PARAMETER">table_name</replaceable> [ * ] [`
`123`	`123`	`The column name can be qualified with a subfield name or array`
`124`	`124`	`subscript, if needed. Do not include the table's name in the`
`125`	`125`	`specification of a target column — for example,`
`126`		`- <literal>UPDATEtab SETtab.col = 1</> is invalid.`
	`126`	`+ <literal>UPDATEtable_name SETtable_name.col = 1</> is invalid.`
`127`	`127`	`</para>`
`128`	`128`	`</listitem>`
`129`	`129`	`</varlistentry>`

Comments

(0)