<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Recent changes to 4: Save with alert search criteria syntax differs from viewer</title><link>https://sourceforge.net/p/lmappletserver/bugs/4/</link><description>Recent changes to 4: Save with alert search criteria syntax differs from viewer</description><atom:link href="https://sourceforge.net/p/lmappletserver/bugs/4/feed.rss" rel="self"/><language>en</language><lastBuildDate>Tue, 27 Jan 2009 07:11:38 -0000</lastBuildDate><atom:link href="https://sourceforge.net/p/lmappletserver/bugs/4/feed.rss" rel="self" type="application/rss+xml"/><item><title>Save with alert search criteria syntax differs from viewer</title><link>https://sourceforge.net/p/lmappletserver/bugs/4/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;When the search is run by com.lightminds.search.alerts.AlertCache.compare(), rather than getLatestLogEntries or searchLogEntries - the search criteria is interpreted differently. The getLatestLogEntries and searchLogEntries methods uses sql like to compare, thus you can use wildcards like % and _ , an these methods are also able to compare strings using &amp;gt; and &amp;lt;. The AlertCache.compare() is only matching equal strings, while it should also match strings that are partially equal from the beginning, just as the viewer. The AlertCache.compare() should also be able to compare strings having &amp;gt; and &amp;lt; in the criteria. The value should only be parsed to a number (Double) when the MetaData is defined as numeric.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Peter Salomonsen</dc:creator><pubDate>Tue, 27 Jan 2009 07:11:38 -0000</pubDate><guid>https://sourceforge.net3036b27b4c70246e0ac78a9b989616bd3907592d</guid></item></channel></rss>