Re: [OT] MySQL is bad, but THIS bad? - Mailing list pgsql-hackers

From Robert Treat
Subject Re: [OT] MySQL is bad, but THIS bad?
Date
Msg-id 200605182015.00260.xzilla@users.sourceforge.net
Whole thread Raw
In response to Re: [OT] MySQL is bad, but THIS bad?  (Philippe Schmid <phschmid@cadinfo.ch>)
Responses Re: [OT] MySQL is bad, but THIS bad?  (Christopher Kings-Lynne <chris.kings-lynne@calorieking.com>)
List pgsql-hackers
On Thursday 18 May 2006 16:17, Philippe Schmid wrote:
> As a users of both Postgres and MySQL, I would also say, better add
> missing features to Postgres than chasing some specialties that are
> going to vanish anyway in MySQL.
> I miss :
> - a core full-text indexing engine. Tsearch2 is nice, but not
> included. This is a feature often used by PHP/MySQL packages.

We also need better support for non C locales in tsearch.  As I was porting 
mysql's sakila sample database I was reminded just how painful it is when you 
initdb in a non-supported locale (which is probably the default on the 
majority of distros out there)

-- 
Robert Treat
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL


pgsql-hackers by date:

Previous
From: "Dawid Kuroczko"
Date:
Subject: Re: [OT] MySQL is bad, but THIS bad?
Next
From: Mark Dilger
Date:
Subject: text_position worst case runtime