Re: Request Tracker ( RT ) recommends MySQL

From: Jan Wieck <JanWieck(at)Yahoo(dot)com>
To: Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>
Cc: Brad Nicholson <bnichols(at)ca(dot)afilias(dot)info>, pgsql-advocacy(at)postgresql(dot)org
Subject: Re: Request Tracker ( RT ) recommends MySQL
Date: 2005-09-29 16:29:32
Message-ID: 433C166C.6060300@Yahoo.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-advocacy

On 9/29/2005 3:44 AM, Christopher Kings-Lynne wrote:

>> I'm the one that Chris mentioned that did the performance tuning on RT.
>> Best Practical are really good people to work with, but they will only
>> use code that will work across all databases the support. There was one
>> query in particular that made really horrible use of OR clauses. I sent
>> in details on how to rewrite the query using unions, which changed it
>> query from a "execute your query and go make coffee" type of query to
>> one that completed in a very reasonable period of time. I was told that
>> it wasn't an option because MySQL didn't have Unions.
>
> MySQL 4 has unions...

... as well as a different license for the client library. Might not be
a problem for RT itself, but you know, some people have multiple
databases with different applications, so 3.x backward support has some
value in it.

Jan

--
#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me. #
#================================================== JanWieck(at)Yahoo(dot)com #

In response to

Responses

Browse pgsql-advocacy by date

  From Date Subject
Next Message Chris Browne 2005-09-29 19:11:22 Re: Request Tracker ( RT ) recommends MySQL
Previous Message Christopher Kings-Lynne 2005-09-29 07:44:58 Re: Request Tracker ( RT ) recommends MySQL