Another option is to use the PCRE (Perl Compatable Regular Expressions) loadable module for SQLite for familar pattern matching via the REGEXP function.
#!/usr/bin/perl
use warnings; use strict;
use 5.10.1;
use DBI;
my $dbh = DBI->connect("dbi:SQLite:dbname=/tmp/text.db", "", "", {Rais
+eError => 1});
# so we can use SQLite REGEXP operator
$dbh->sqlite_enable_load_extension(my $_enabled = 1);
$dbh->prepare("SELECT load_extension('/usr/lib/sqlite3/pcre.so')");
my $word = 'tag';
my $word_re = '\b'.quotemeta($word).'\b';
my $results = $dbh->selectall_arrayref("SELECT ID, sentence FROM tex
+ts WHERE sentence REGEXP ?", {}, $word_re);
foreach my $result (@$results) {
my ($id, $sentence) = @$result;
say "matched $id: $sentence";
}
Depending on your system it may be available as a package (Ubuntu has sqlite3-pcre).
It's also available from github https://github.com/oojah/sqlite3-pcre where you can build and install it yourself.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|