From: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
---|---|
To: | John Gage <jsmgage(at)numericable(dot)fr> |
Cc: | PGSQL Mailing List <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Differences between Postgres and MySql |
Date: | 2010-07-18 21:41:21 |
Message-ID: | AANLkTimjLM-QxFyZ_iEEWtbFTgCy-7IjiKTN8vi9lObw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Sun, Jul 18, 2010 at 2:13 PM, John Gage <jsmgage(at)numericable(dot)fr> wrote:
>> John Gage, 25.06.2010 11:50:
>>>
>>> I am astonished to discover that MySQL does not support
>>> regular expressions much less something like tsvector.
>>
>> Getting really off-topic now: but MySQL does support Regex
>>
>> http://dev.mysql.com/doc/refman/5.1/en/regexp.html
>
> I have done an extensive comparison between MySQL's support for regexp and
> Postresql's and, frankly, there is no comparison. The support in Postgresql
> is far greater than in MySQL. This is not a flame. It is intended to help
> anyone choosing between the two programs.
>
> The best example I can present is the regexp_split_to_table function in
> Postgres. I use it all the time. It is enormously convenient. Anyone
> analyzing text is ecstatic to have such a powerful function readily
> available.
>
> This is a qualitative difference.
That and array_accum (in the docs in 8.3 I think it's built in now)
make life a breaze for making reports. No need for post query data
mangling, I get it out just the way I need it.
From | Date | Subject | |
---|---|---|---|
Next Message | Irooniam | 2010-07-18 21:41:41 | xpath index not being used |
Previous Message | Michael Friedrich | 2010-07-18 21:34:50 | Re: NASA needs Postgres - Nagios help |