Add support for PostgreSQL regex match

[b41sh]

Support PostgreSQL regular expression matching syntax as described in the Postgres manual: https://www.postgresql.org/docs/9.3/functions-matching.html

used by arrow-datafusion#795

[alamb]

cc @Dandandan / @andygrove

[coveralls]

Pull Request Test Coverage Report for Build 1141922167

Warning: This coverage report may be inaccurate.

This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

• For more information on this, see Tracking coverage changes with pull request builds.
• To avoid this issue with future PRs, see these Recommended CI Configurations.
• For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

• 71 of 84 (84.52%) changed or added relevant lines in 8 files are covered.
• 9 unchanged lines in 3 files lost coverage.
• Overall coverage decreased (-0.2%) to 90.034%

---

Changes Missing Coverage	Covered Lines	Changed/Added Lines	%
src/ast/mod.rs	1	5	20.0%
src/parser.rs	5	9	55.56%
src/tokenizer.rs	43	48	89.58%

Files with Coverage Reduction	New Missed Lines	%
src/parser.rs	1	85.78%
tests/sqlparser_postgres.rs	1	99.69%
tests/sqlparser_common.rs	7	98.66%

Totals
Change from base Build 1040258090:	-0.2%
Covered Lines:	5529
Relevant Lines:	6141

---

💛 - Coveralls

[alamb]

This looks great @b41sh -- FYI I pulled your code down locally to play around with it and tried to fix the clippy errors on CI while I was at it, in case that is helpful to you: https://github.com/b41sh/sqlparser-rs/pull/1

[alamb]

👍 this is quite cool

[b41sh]

This looks great @b41sh -- FYI I pulled your code down locally to play around with it and tried to fix the clippy errors on CI while I was at it, in case that is helpful to you: b41sh#1

@alamb Thanks for your help. But I have a question, why I run cargo clippy in my local environment doesn't report any errors or warnings?

[alamb]

@alamb Thanks for your help. But I have a question, why I run cargo clippy in my local environment doesn't report any errors or warnings?

@b41sh I don't honestly know / understand. I also had trouble getting clippy to report all errors locally for me until I switched to running it like this

find . -name '*.rs' | grep -v target | xargs touch && cargo clippy --all --all-targets -- -D warnings

While not ideal (it forces a recheck), it does work reliably for me

[b41sh]

@b41sh I don't honestly know / understand. I also had trouble getting clippy to report all errors locally for me until I switched to running it like this

find . -name '*.rs' | grep -v target | xargs touch && cargo clippy --all --all-targets -- -D warnings

While not ideal (it forces a recheck), it does work reliably for me

ok, I will try it