A small off-topic piece of advice:
SELECT * FROM tblBlogPosts WHERE fldTags LIKE '%?%'
Beware the performance implications of using Wildcard characters and the LIKE operator:
Under most circumstances, the original LIKE or GLOB operator is still tested against each input row ..
This means your database backend must do a full table scan for every query. As the database grows, the queries will take increasingly long time to complete.

Disclaimer: I've no experience with SQLLite. The above applies to all other database I know of: MySQL, Postgres, Oracle, DB2, SQL Server.

--
print map{chr}unpack(q{A3}x24,q{074117115116032097110111116104101114032080101114108032104097099107101114})

In reply to Re: DBI:SQLite bind_param problem by andreas1234567
in thread DBI:SQLite bind_param problem by davehope

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.