> Thank you for the information. I was hoping that it was something
> like that. Stick with your areas of expertise to reduce support
> costs. We are more the other way here with more PostgreSQL than
> MySQL. What is your plan to provide redundancy/business continuity
> for your RT instance and wha
On Fri, Mar 13, 2009 at 02:10:08PM +, Kristian Davies wrote:
> > It does sound like something is missing because I am running
> > PostgreSQL 8.3.5 and did not have to make these changes. I do have
> > a question, why are you converting your RT instance to MySQL? Is
> > there a particular proble
> It does sound like something is missing because I am running
> PostgreSQL 8.3.5 and did not have to make these changes. I do have
> a question, why are you converting your RT instance to MySQL? Is
> there a particular problem you are trying to address?
No technical reason, we are a essentially a
On Fri, Mar 13, 2009 at 12:42:11AM +, Kristian Davies wrote:
> On Thu, Mar 12, 2009 at 1:51 PM, Kenneth Marshall wrote:
> > On Thu, Mar 12, 2009 at 08:44:23AM -0500, Kenneth Marshall wrote:
> >> Kristian,
> >>
> >> I think the problem is in SearchBuilder/Handle.pm in the function
> >> _MakeCla
On Thu, Mar 12, 2009 at 1:51 PM, Kenneth Marshall wrote:
> On Thu, Mar 12, 2009 at 08:44:23AM -0500, Kenneth Marshall wrote:
>> Kristian,
>>
>> I think the problem is in SearchBuilder/Handle.pm in the function
>> _MakeClauseCaseInsensitive. It looks like it only skips the lower()
>> for integer va
On Thu, Mar 12, 2009 at 08:44:23AM -0500, Kenneth Marshall wrote:
> Kristian,
>
> I think the problem is in SearchBuilder/Handle.pm in the function
> _MakeClauseCaseInsensitive. It looks like it only skips the lower()
> for integer values. I think that you can replace the if test with
> something
Kristian,
I think the problem is in SearchBuilder/Handle.pm in the function
_MakeClauseCaseInsensitive. It looks like it only skips the lower()
for integer values. I think that you can replace the if test with
something like:
if ($value !~ /^[\d:- ]+$/) { # don't downcase integer values or timest
It looks like the problem is caused by trying to change the
case of a timestamp, which is nonsensical. Could you send me
a sample advanced search input that I could try with my setup
and queues to see if I can reproduce the problem locally?
You could also define a lower() function that does nothing
Unfortunately I'd already tried those. I did however get excellent
results from your full text search wiki page though.
Mar 12 12:48:19 ghole postgres[13129]: [2-1] ERROR: function
lower(timestamp without time zone) does not exist at character 259
Mar 12 12:48:19 ghole postgres[13129]: [2-2] H
On Thu, Mar 12, 2009 at 11:00:21AM +, Kristian Davies wrote:
> Postgres: 8.3.6
> RT 3.8.2
> CentOS 4
>
> My graphing isn't working under Tools>Reports.
>
> Any ideas?
>
> Cheers,
> Kristian
>
>
> /var/log/message
>
> Mar 12 10:50:27 ghole postgres[11326]: [2-1] ERROR: function
> lower(ti
Postgres: 8.3.6
RT 3.8.2
CentOS 4
My graphing isn't working under Tools>Reports.
Any ideas?
Cheers,
Kristian
/var/log/message
Mar 12 10:50:27 ghole postgres[11326]: [2-1] ERROR: function
lower(timestamp without time zone) does not exist at character 315
Mar 12 10:50:27 ghole postgres[11326]:
11 matches
Mail list logo
