On Tue, Jan 26, 2010 at 02:12:34PM -0600, Kenneth Marshall wrote: > Moving from PostgreSQL -> MySQL will need a little bit more work. > I think that there is a wiki article and possibly some tools to > help with this process. I do have a question for you. Why are you > moving from PostgreSQL to MySQL instead of updating to the current > PostgreSQL release? For one thing, PostgreSQL will allow you to > use full text indexing to dramatically improve the performance of > full content searching within your tickets and RTFM articles. > This functionality is also available with the Oracle backend. Is > there some problem you are trying to address?
Just to note that I assume you're talking about <http://wiki.bestpractical.com/view/PostgreSQLFullText> which isn't a standard part of RT yet; I wondered for a while after reading your message whether I'd missed something! It's a shame that the API for SearchBuilder isn't such that you can configure to treat certain columns as full-text-searchable ones rather than have to manually hack it in; makes deployment a little more fiddly. But thanks for mentioning it because I didn't realise that this work had been done and it's something we're interested in! -- Dominic Hargreaves, Systems Development and Support Team Computing Services, University of Oxford
signature.asc
Description: Digital signature
_______________________________________________ http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users Community help: http://wiki.bestpractical.com Commercial support: sa...@bestpractical.com 2010 RT Training Sessions! San Francisco, CA, USA - Feb 22 & 23 Dublin, Ireland - Mar 15 & 16 Boston, MA, USA - April 5 & 6 Washington DC, USA - Oct 25 & 26 Discover RT's hidden secrets with RT Essentials from O'Reilly Media. Buy a copy at http://rtbook.bestpractical.com
