<?xml version="1.0"?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
  <channel>
    <title>CKAN: Ticket #249: Regex search</title>
    <link>http://localhost/ticket/249</link>
    <description>&lt;p&gt;
Search of package name and title (and other fields) using regular expressions.
&lt;/p&gt;
&lt;p&gt;
Current example use-case: Wanting to specify packages with title beginning with 'B'.
&lt;/p&gt;
&lt;p&gt;
Issues:
&lt;/p&gt;
&lt;ul&gt;&lt;li&gt;Syntax for specifying regex over natural language search - could it be contained in the q param so be available to users of the WUI, or do we simply make it alternative fields?
&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;
Implementation:
&lt;/p&gt;
&lt;ul&gt;&lt;li&gt;Postgres reg ex searching detailed here:
&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;
&lt;a class="ext-link" href="http://www.postgresql.org/docs/current/static/functions-matching.html#FUNCTIONS-POSIX-TABLE"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;http://www.postgresql.org/docs/current/static/functions-matching.html#FUNCTIONS-POSIX-TABLE&lt;/a&gt;
&lt;/p&gt;
</description>
    <language>en-us</language>
    <image>
      <title>CKAN</title>
      <url>http://assets.okfn.org/p/ckan/img/ckan_logo_shortname.png</url>
      <link>http://localhost/ticket/249</link>
    </image>
    <generator>Trac 0.12.3</generator>
    <item>
      
        <dc:creator>thejimmyg</dc:creator>

      <pubDate>Wed, 20 Jul 2011 17:20:50 GMT</pubDate>
      <title>status changed; repo, theme, resolution set</title>
      <link>http://localhost/ticket/249#comment:1</link>
      <guid isPermaLink="false">http://localhost/ticket/249#comment:1</guid>
      <description>
          &lt;ul&gt;
            &lt;li&gt;&lt;strong&gt;repo&lt;/strong&gt;
                set to &lt;em&gt;ckan&lt;/em&gt;
            &lt;/li&gt;
            &lt;li&gt;&lt;strong&gt;status&lt;/strong&gt;
                changed from &lt;em&gt;new&lt;/em&gt; to &lt;em&gt;closed&lt;/em&gt;
            &lt;/li&gt;
            &lt;li&gt;&lt;strong&gt;theme&lt;/strong&gt;
                set to &lt;em&gt;none&lt;/em&gt;
            &lt;/li&gt;
            &lt;li&gt;&lt;strong&gt;resolution&lt;/strong&gt;
                set to &lt;em&gt;invalid&lt;/em&gt;
            &lt;/li&gt;
          &lt;/ul&gt;
        &lt;p&gt;
This is over 6 months old so closing in line with our ticketing policy. Also, I shouldn't think we really want such a complicated search anyway.
&lt;/p&gt;
      </description>
      <category>Ticket</category>
    </item>
 </channel>
</rss>