Movatterモバイル変換

[0]ホーム
URL:

Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

 Sign up
Appearance settings

Commitfdae4a9

Browse files
committed
Remove obsolete advice about doubling backslashes in regex escapes.
Standard-conforming literals have been the default for long enough thatit no longer seems necessary to go out of our way to tell people to writeregex escapes illegibly.
1 parentf4057cd commitfdae4a9

File tree

1 file changed

+0
-10
lines changed

1 file changed

+0
-10
lines changed

‎doc/src/sgml/func.sgml‎

Lines changed: 0 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -4642,16 +4642,6 @@ SELECT foo FROM regexp_split_to_table('the quick brown fox', E'\\s*') AS foo;
46424642
Non-capturing parentheses do not define subexpressions.
46434643
</para>
46444644

4645-
<note>
4646-
<para>
4647-
Keep in mind that an escape's leading <literal>\</> will need to be
4648-
doubled when entering the pattern as an SQL string constant. For example:
4649-
<programlisting>
4650-
'123' ~ E'^\\d{3}' <lineannotation>true</lineannotation>
4651-
</programlisting>
4652-
</para>
4653-
</note>
4654-
46554645
<table id="posix-character-entry-escapes-table">
46564646
<title>Regular Expression Character-entry Escapes</title>
46574647

0 commit comments

Comments
 (0)
[8]ページ先頭
©2009-2025 Movatter.jp