While almost all occurrences of "case-insensitive{ly}" were spelled with
a dash, a few were using "case insensitive{ly}" with a space instead. Fix
by changing these to use a dash to be consistent.
Discussion: https://postgr.es/m/
7657EDEE-5EE2-4AAB-BA95-
47B4F71653E1@yesql.se
index 053d4dc650b6c215ccd1bf4a74631938b4fb96e5..8dd63c04556106db982eaf33a416a6bc2ddf301a 100644 (file)
@@ -5604,7 +5604,7 @@ substring('foobar' similar '#"o_b#"%' escape '#') <lineannotation>NULL</linea
<returnvalue>boolean</returnvalue>
</para>
<para>
- String matches regular expression, caseinsensitively
+ String matches regular expression, case-insensitively
</para>
<para>
<literal>'thomas' ~* 'T.*ma'</literal>
@@ -5632,7 +5632,7 @@ substring('foobar' similar '#"o_b#"%' escape '#') <lineannotation>NULL</linea
<returnvalue>boolean</returnvalue>
</para>
<para>
- String does not match regular expression, caseinsensitively
+ String does not match regular expression, case-insensitively
</para>
<para>
<literal>'thomas' !~* 'T.*ma'</literal>
index 71d644f43234513a60baaea87fe6866accd6ba62..6f31a5a1d621c0cbe94892ca8c7f37a58a9399bd 100644 (file)
differently than above, or even all on one line. Two dashes
(<quote><literal>--</literal></quote>) introduce comments.
Whatever follows them is ignored up to the end of the line. SQL
- is caseinsensitive about key words and identifiers, except
+ is case-insensitive about key words and identifiers, except
when identifiers are double-quoted to preserve the case (not done
above).
</para>
index a99c24373e44553270370933d544b0aac22600d4..93ad71737f51383291b37bc1bf79e1ac59f81f0e 100644 (file)
@@ -144,7 +144,7 @@ INSERT INTO MY_TABLE VALUES (3, 'hi there');
<primary>case sensitivity</primary>
<secondary>of SQL commands</secondary>
</indexterm>
- Key words and unquoted identifiers are caseinsensitive. Therefore:
+ Key words and unquoted identifiers are case-insensitive. Therefore:
<programlisting>
UPDATE MY_TABLE SET A = 5;
</programlisting>