When our customer runs Crystal Reports reports created in an old version
of CR and edited with CR XI, he gets a large number of warnings in his
Postgres log files that look like this:
2010-10-05 11:28:00 EDTWARNING: nonstandard use of \\ in a string
literal at character 159
2010-10-05 11:28:00
Dear Rob ,
this will give warning:
SELECT co_name from foo where co_name ilike '%\\_%' limit 10;
and this will not:
SELECT co_name from foo where co_name ilike E'%\\_%' limit 10;
regds
Rajesh Kumar Mallah.
Dear Rob,
Please do not go offlist.
Its not a matter of cancelling,
consider the fragment -- relname like 'coil\\_status'
the underscore has to be escaped because if its not done
'_' will match any *single* character (rule of ilike matching) ,
its escaped so that it matches '_' in strings.
Can anyone tell me if there is some setting that will stop these warnings
from showing up (other than turning off warning messages completely, which I
am about to suggest that the customer do)? Also, does anyone know why my
computer is not showing warnings while our customer's system is?
