RT 3.4.0 rc's not completing search queries on customfields?

Looks like ObjectCustomFieldValues is the correct table name. (It’s
renamed from TicketCustomFieldValues in the upgrade schema files in
etc/upgrade/3.3.0 for mysql, pgsql and Oracle.) I wonder why the same
change wasn’t made for the other supported databases?

MarkR-----Original Message-----
From: rt-users-bounces@lists.bestpractical.com
[mailto:rt-users-bounces@lists.bestpractical.com] On Behalf Of David
Snyder
Sent: Friday, January 07, 2005 10:34 AM
To: rt-users@lists.bestpractical.com
Cc: rt-bugs@fsck.com
Subject: Re: [rt-users] RT 3.4.0 rc’s not completing search queries on
customfields?

[Fri Jan 07 11:15:26 2005] [error] [client 130.132.101.242] FastCGI:
server “/opt/rt3.4/bin/mason_handler.fcgi” stderr: DBD::mysql::st
execute failed: Table ‘rt34.TicketCustomFieldValues’ doesn’t exist at
/usr/local/perl-5.8.5/lib/site_perl/5.8.5/DBIx/SearchBuilder/Handle.pm
line 475., referer:
http://fasit-rhel1.its.yale.edu/rt3.4/Search/Edit.html?Order=ASC&Query=%
20’CF.%7BType%7D’%20%3D%20’problem’%20&Rows=50&OrderBy=id&Format=’%20%20
%20%3Cb%3E%3Ca%20href%3D%22%2Frt3.4%2FTicket%2FDisplay.html%3Fid%3D__id_
%22%3E__id_%3C%2Fa%3E%3C%2Fb%3E%2FTITLE%3A%23’%2C%0A’%3Cb%3E%3Ca%20hre
f%3D%22%2Frt3.4%2FTicket%2FDisplay.html%3Fid%3D__id__%22%3E__Subject__%3
C%2Fa%3E%3C%2Fb%3E%2FTITLE%3ASubject’%2C%0A’Status’%2C%0A’QueueNam
e
’%2C%0A’OwnerName’%2C%0A’Priority’%2C%0A’NEWLINE’%2C%0A’’
%2C%0A’%3Csmall%3E__Requestors__%3C%2Fsmall%3E’%2C%0A’%3Csmall%3E__Creat
edRelative__%3C%2Fsmall%3E’%2C%0A’%3Csmall%3E__ToldRelative__%3C%2Fsmall
%3E’%2C%0A’%3Csmall%3E__LastUpdatedRelative__%3C%2Fsmall%3E’%2C%0A’%3Csm
all%3E__TimeLeft__%3C%2Fsmall%3E’

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.

David

http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users

Be sure to check out the RT wiki at http://wiki.bestpractical.com

Looks like ObjectCustomFieldValues is the correct table name. (It’s
renamed from TicketCustomFieldValues in the upgrade schema files in
etc/upgrade/3.3.0 for mysql, pgsql and Oracle.) I wonder why the same
change wasn’t made for the other supported databases?

The change should have been made for every supported database. SQLite,
MySQL, Postgresql and Oracle.