[rt-users] RT 3.4.0 rc's not completing search queries on custom fields?

David Snyder david.w.snyder at yale.edu
Fri Jan 7 11:34:27 EST 2005

>> I'm assuming this is something specific to my system, since I can't
>> imagine we'd have made it to release candidates without something that
>> major still outstanding.  (Although if someone else is able to duplicate
>> it, I'll be all ears...)
> It looks like this can be reproduced on rt3.fsck.com - a search in the 
> rt2.0 queue for subsystem = 'HTML::Mason frontend' yields no results, 
> whereas there is at least one ticket in the queue (#2) that matches.
> One more datapoint - I'm running 3.3.12 and the feature works in that 
> version, at least on queue/ticket CFs.
>> I'm just not sure where to start with
>> troubleshooting.
> If you have a perl script (and some spare time!), how about stepping 
> through with the debugger?
> Steve
 From my apache error log when I try to search on a Ticket Custom Field:
[Fri Jan 07 11:15:26 2005] [error] [client] FastCGI: 
server "/opt/rt3.4/bin/mason_handler.fcgi" stderr: DBD::mysql::st 
execute failed: Table 'rt34.TicketCustomFieldValues' doesn't exist at 
line 475., referer: 

I found that the TicketCustomFieldValues is not defined in schema.mysql, 
only in schema.Informix and schema.Sybase.    Also, mysql, Oracle, Pg, 
and SQLite have and ObjectCustomFieldValues tables, where Informix and 
Sybase do not.  I'm not smart enought to figure out which is right 
though, or how to translate from Informix or Sybase syntax to mysql to 
create the table.


More information about the rt-users mailing list