public inbox for [email protected]help / color / mirror / Atom feed
Addition to / Clarification in 9.7.1. LIKE 4+ messages / 3 participants [nested] [flat]
* Addition to / Clarification in 9.7.1. LIKE @ 2017-12-14 09:33 [email protected] 0 siblings, 1 reply; 4+ messages in thread From: [email protected] @ 2017-12-14 09:33 UTC (permalink / raw) To: pgsql-docs The following documentation comment has been logged on the website: Page: https://www.postgresql.org/docs/10/static/functions-matching.html Description: Between the 1st and 2nd paragraphs please add a new one which make clear (also to a newbie like myself) that the _only characters_ can be used in pattern are (_) and (%). Tia ^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: Addition to / Clarification in 9.7.1. LIKE @ 2018-01-25 22:55 Bruce Momjian <[email protected]> parent: [email protected] 0 siblings, 1 reply; 4+ messages in thread From: Bruce Momjian @ 2018-01-25 22:55 UTC (permalink / raw) To: [email protected]; +Cc: pgsql-docs On Thu, Dec 14, 2017 at 09:33:39AM +0000, [email protected] wrote: > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/10/static/functions-matching.html > Description: > > Between the 1st and 2nd paragraphs please add a new one which make clear > (also to a newbie like myself) that the _only characters_ can be used in > pattern are (_) and (%). Uh, it is not totally clear what you are suggesting here. I think you are talking about the LIKE command and its use of _ and %. What detail should be added? Can you show an example? -- Bruce Momjian <[email protected]> http://momjian.us EnterpriseDB http://enterprisedb.com + As you are, so once was I. As I am, so you will be. + + Ancient Roman grave inscription + ^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: Addition to / Clarification in 9.7.1. LIKE @ 2018-01-26 08:52 GPT <[email protected]> parent: Bruce Momjian <[email protected]> 0 siblings, 1 reply; 4+ messages in thread From: GPT @ 2018-01-26 08:52 UTC (permalink / raw) To: Bruce Momjian <[email protected]>; +Cc: pgsql-docs Between 1st (The LIKE expression...) and 2nd (If pattern does not...) paragraphs, it could be added something like: <begin> Caution Contrary to some other databases, in Postgresql only two characters are used in LIKE patterns: underscore (_) and percent sign (%). The use of any other character will lead to an error. <end> The error message also would be more clarified to inform user about the use of not supported characters. On 1/25/18, Bruce Momjian <[email protected]> wrote: > On Thu, Dec 14, 2017 at 09:33:39AM +0000, [email protected] wrote: >> The following documentation comment has been logged on the website: >> >> Page: https://www.postgresql.org/docs/10/static/functions-matching.html >> Description: >> >> Between the 1st and 2nd paragraphs please add a new one which make clear >> (also to a newbie like myself) that the _only characters_ can be used in >> pattern are (_) and (%). > > Uh, it is not totally clear what you are suggesting here. I think you > are talking about the LIKE command and its use of _ and %. What detail > should be added? Can you show an example? > > -- > Bruce Momjian <[email protected]> http://momjian.us > EnterpriseDB http://enterprisedb.com > > + As you are, so once was I. As I am, so you will be. + > + Ancient Roman grave inscription + > ^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: Addition to / Clarification in 9.7.1. LIKE @ 2018-01-26 13:22 Bruce Momjian <[email protected]> parent: GPT <[email protected]> 0 siblings, 0 replies; 4+ messages in thread From: Bruce Momjian @ 2018-01-26 13:22 UTC (permalink / raw) To: GPT <[email protected]>; +Cc: pgsql-docs On Fri, Jan 26, 2018 at 09:52:07AM +0100, GPT wrote: > Between 1st (The LIKE expression...) and 2nd (If pattern does not...) > paragraphs, it could be added something like: > > <begin> > Caution > Contrary to some other databases, in Postgresql only two characters > are used in LIKE patterns: underscore (_) and percent sign (%). > The use of any other character will lead to an error. > <end> > > The error message also would be more clarified to inform user about > the use of not supported characters. Uh, I still don't understand what error you are talking about. Here are some examples: SELECT 'abc' LIKE 'a_c'; ?column? ---------- t SELECT 'abc' LIKE 'a%c'; ?column? ---------- t SELECT 'abc' LIKE 'a%*c'; ?column? ---------- f Can you show me an example? -- Bruce Momjian <[email protected]> http://momjian.us EnterpriseDB http://enterprisedb.com + As you are, so once was I. As I am, so you will be. + + Ancient Roman grave inscription + ^ permalink raw reply [nested|flat] 4+ messages in thread
end of thread, other threads:[~2018-01-26 13:22 UTC | newest] Thread overview: 4+ messages (download: mbox mbox.gz follow: Atom feed) -- links below jump to the message on this page -- 2017-12-14 09:33 Addition to / Clarification in 9.7.1. LIKE [email protected] 2018-01-25 22:55 ` Bruce Momjian <[email protected]> 2018-01-26 08:52 ` GPT <[email protected]> 2018-01-26 13:22 ` Bruce Momjian <[email protected]>
This inbox is served by agora; see mirroring instructions for how to clone and mirror all data and code used for this inbox