Commit25bf317

committed

Doc: explain that LIKE et al can be used in ANY (sub-select) etc.

This wasn't stated anywhere, and it's perhaps not that obvious,since we get questions about it from time to time. Also undocumentedwas that the parser actually translates these into operators.Discussion:https://postgr.es/m/CAFj8pRBkvZ71BqGKZnBBG4=0cKG+s50Dy+DYmrizUKEpAtdc+w@mail.gmail.com

1 parentaae7e85 commit25bf317Copy full SHA for 25bf317

File tree

+17

-1

lines changed

+17

-1

lines changed

Lines changed: 17 additions & 1 deletion

Original file line number	Diff line number	Diff line change
`@@ -4046,7 +4046,23 @@ cast(-44 as bit(12)) <lineannotation>111111010100</lineannotation>`
`4046`	`4046`	`<literal>!~~</literal> and <literal>!~~*</literal> operators that`
`4047`	`4047`	`represent <function>NOT LIKE</function> and <function>NOT`
`4048`	`4048`	`ILIKE</function>, respectively. All of these operators are`
`4049`		`- <productname>PostgreSQL</productname>-specific.`
	`4049`	`+ <productname>PostgreSQL</productname>-specific. You may see these`
	`4050`	`+ operator names in <command>EXPLAIN</command> output and similar`
	`4051`	`+ places, since the parser actually translates <function>LIKE</function>`
	`4052`	`+ et al. to these operators.`
	`4053`	`+ </para>`
	`4054`	`+`
	`4055`	`+ <para>`
	`4056`	`+ The phrases <function>LIKE</function>, <function>ILIKE</function>,`
	`4057`	`+ <function>NOT LIKE</function>, and <function>NOT ILIKE</function> are`
	`4058`	`+ generally treated as operators`
	`4059`	`+ in <productname>PostgreSQL</productname> syntax; for example they can`
	`4060`	`+ be used in <replaceable>expression</replaceable>`
	`4061`	`+ <replaceable>operator</replaceable> ANY`
	`4062`	`+ (<replaceable>subquery</replaceable>) constructs, although`
	`4063`	`+ an <literal>ESCAPE</literal> clause cannot be included there. In some`
	`4064`	`+ obscure cases it may be necessary to use the underlying operator names`
	`4065`	`+ instead.`
`4050`	`4066`	`</para>`
`4051`	`4067`
`4052`	`4068`	`<para>`

Comments

(0)