Thanks! It worked with %% instead of %. (And without the where
condition, but I want to match comp% so comp%% works great).
Thanks Russ and Noah!
--Jennifer
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Trac
Us
On Fri, 2006-09-15 at 01:50 +, [EMAIL PROTECTED] wrote:
> Strange! It's exactly what I ran, but I didn't get any tickets. Instead
> I get: "Report execution failed: list index out of range" in a red box
> in the reports page. Did you try running it as a report?
>
> Maybe there is something wr
Minor point of note: just remove the whole condition to get the same
effect with less overhead. Also try using %% instead of %.
--Noah
On Sep 14, 2006, at 8:29 PM, [EMAIL PROTECTED] wrote:
>
> I'm fairly new to generating my own reports (and to SQL in
> general), so
> I may be missing somet
Strange! It's exactly what I ran, but I didn't get any tickets. Instead
I get: "Report execution failed: list index out of range" in a red box
in the reports page. Did you try running it as a report?
Maybe there is something wrong with my database or trac reporting
module?
--Jennifer
--~--~---
On Fri, 2006-09-15 at 00:29 +, [EMAIL PROTECTED] wrote:
> I'm fairly new to generating my own reports (and to SQL in general), so
> I may be missing something obvious, but is the LIKE syntax supported
> for reports? I can't seem to get it to work. We are using postgres as
> the Track DB.
>
>
