Trouble with regexp_matches

From: Edson Richter <edsonrichter(at)hotmail(dot)com>
To: "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Trouble with regexp_matches
Date: 2016-11-05 17:01:01
Message-ID: CY1PR01MB18180319106339B77C1D4AEFCFA50@CY1PR01MB1818.prod.exchangelabs.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Dear list,

Version string PostgreSQL 9.4.10 on x86_64-unknown-linux-gnu, compiled by gcc (GCC) 4.8.5 20150623 (Red Hat 4.8.5-4), 64-bit

I’m running the query below, and it is limiting results as if “regexp_matches” being in where clause.
IMHO, it is wrong: in case there is no match, shall return null or empty array – not remove the result from the set!!!

Is this a collateral effect of using regexp_matches in columns?
If yes, shall not this information be BOLD RED FLASHING in documentation (or it is already, and some kind sould would point me where)?

-- First query (that is limiting results) ---------------------------------------------------------------------
select codigoocorrencia, datahoraocorrencia, datahoraimportacao, observacao, regexp_matches(observacao, '\d\d/\d\d/\d\d\d\d')
from batchloteocorrencia
where codigoocorrencia = '091'
and observacao is not null
order by datahoraimportacao DESC

Total results = 59

--Second query (that is not limiting results, as I did expect)-------------------------------------------------------------------
select codigoocorrencia, datahoraocorrencia, datahoraimportacao, observacao
from batchloteocorrencia
where codigoocorrencia = '091'
and observacao is not null
order by datahoraimportacao DESC

Total results = 3826

Why is that?

Regards,

Edson Richter

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Adrian Klaver 2016-11-05 17:13:25 Re: Trouble with regexp_matches
Previous Message btober@computer.org 2016-11-05 00:45:20 Re: What is the best thing to do with PUBLIC schema in Postgresql database