Just be sure to check .. on *very large* record sets .
by using constructs like this :-
lower(Comments) like '%coral%'
upper(Comments) like '%CORAL%'
you may prevent the underlying database from using any indexes on, in this case, the 'Comments' column. The index may be case sensitive, and as soon as the DB sees a function applied to column in may not be able to rely on the index and so will often ignore it, forcing a full table scan and causing a potential performance hit.
May not apply in your case .. just a heads up
