#2773: Report fails because of complex SQL
---------------------------------+------------------------------------------
Reporter: [EMAIL PROTECTED] | Owner: mgood
Type: defect | Status: assigned
Priority: normal | Milestone:
Component: report system | Version: 0.9.4
Severity: normal | Resolution:
Keywords: |
---------------------------------+------------------------------------------
Comment (by Piotr Banasik <[EMAIL PROTECTED]>):
This is still a prety major regression the way I see it .. but I found a
new workaround ..
the example above uses $USER which you don't really have control over, but
if you're experiencing this issue with manual custom variables, you can
include the %'s on the url, eg: {{{ ?MILESTONE=%25foo%25 }}} (url encoded
% is %25), and then in the report just use {{{ WHERE milestone like
'$MILESTONE' }}}. This seems to be valid in 0.9.6, I vaguely remember that
%'s in custom variables were a big nono in previous versions.
--
Ticket URL: <http://trac.edgewall.org/ticket/2773#comment:11>
The Trac Project <http://trac.edgewall.com/>
_______________________________________________
Trac-Tickets mailing list
[email protected]
http://lists.edgewall.com/mailman/listinfo/trac-tickets
