I'm upgrading from 3.6.1 and although I could swear I got further than
this on a previous attempt, I am getting :
[Thu Mar 13 19:16:40 2014] [critical]: DBD::mysql::st execute failed:
Duplicate key name 'CachedGroupMembers3' at
/usr/share/request-tracker4/lib/RT/Handle.pm line 515.
(/usr/shar
Referring to: rt-users Digest, Vol 120, Issue 13, articles 8,9,10,11,13,14,15:
Thanks to those who responded. First, no; I did not know that full text
indexing was supported after 5.0. I thought that was a 5.6 up & coming feature.
I must not have a full grasp of how it works, because if MySQL
Cena, Stephen (ext. 300) ha scritto:
We currently run two RT 4.0.19 systems on Ubuntu 12.04LTS and MySQL 5.5.35.
Management is now asking me to enable full text searching on the sites so we
can search inside the body of the tickets. From what I've read, our current
configuration won't support it
On Thu, 2014-03-13 at 14:47 +, Mark Goodge wrote:
> I know that RT uses InnoDB by default but there should be no reason why
> the table you want to search can't be converted to MyISAM.
There's a very straightforward reason why RT uses InnoDB: database-level
transactions. Converting the Attach
On Thu, Mar 13, 2014 at 02:47:10PM +, Mark Goodge wrote:
> On 13/03/2014 14:32, Kevin Falcone wrote:
> >On Thu, Mar 13, 2014 at 02:06:40PM +, Mark Goodge wrote:
> >>On 13/03/2014 14:00, Cena, Stephen (ext. 300) wrote:
> >>>We currently run two RT 4.0.19 systems on Ubuntu 12.04LTS and MySQL
On 13/03/2014 14:32, Kevin Falcone wrote:
On Thu, Mar 13, 2014 at 02:06:40PM +, Mark Goodge wrote:
On 13/03/2014 14:00, Cena, Stephen (ext. 300) wrote:
We currently run two RT 4.0.19 systems on Ubuntu 12.04LTS and MySQL
5.5.35. Management is now asking me to enable full text searching on th
On Thu, Mar 06, 2014 at 10:42:39AM -0600, Tim Wilson wrote:
>We have two queues in RT. All email-generated tickets go into General, and
> we maintain a
>separate Repair queue for our repair department. Tickets are created in
> that queue only by
>tech staff.
>How can we prevent th
I personally went the Sphinx route because I already have so much MySQL running
(and familiarity with) here.
I documented most of it here:
http://parishnetworks.blogspot.com/2013/10/using-mysql-and-sphinx-for-rt-full-text.html
- Brent
-Original Message-
From: rt-users-boun...@lists.
On Thu, Mar 13, 2014 at 02:06:40PM +, Mark Goodge wrote:
> On 13/03/2014 14:00, Cena, Stephen (ext. 300) wrote:
> > We currently run two RT 4.0.19 systems on Ubuntu 12.04LTS and MySQL
> > 5.5.35. Management is now asking me to enable full text searching on the
> > sites so we can search inside
On 13/03/2014 14:00, Cena, Stephen (ext. 300) wrote:
We currently run two RT 4.0.19 systems on Ubuntu 12.04LTS and MySQL
5.5.35. Management is now asking me to enable full text searching on the
sites so we can search inside the body of the tickets. From what I've
read, our current configuration w
We currently run two RT 4.0.19 systems on Ubuntu 12.04LTS and MySQL 5.5.35.
Management is now asking me to enable full text searching on the sites so we
can search inside the body of the tickets. From what I've read, our current
configuration won't support it due to MySQL 5.5.x not supporting it
Hello Alex,
Thank you for all the infos. So:
- we would join improving REST 2.0 (rtx-rest),
- we would develope an angularjs (or backbone.js) client.
I hope our work would be useful for all the RT community.
Hello Community,
If anyone has angularJS or backbone.js competency and could join us (a
12 matches
Mail list logo
