It is indeed an interaction between Ima::DBI's use of prepare_cached and SQLite's changed error. Invalidating the $dbh->{CachedKids} is a passable work-around. I tried and failed to globally turn caching off in Ima::DBI::set_sql, but that probably would have caused performance issues anyway. I'm still not sure exactly which change revealed this problem.

DBD::SQLite seems to be the correct place to address this issue. Does anyone else have an opinion on that matter? Is there a better forum for DBD::SQLite discussions? The only other seems to be RT.
$dbh->{CachedKids} = {}; # after ANALYZE or similar # from the example $dbh->prepare_cached('select "hello" from a'); print Dump $dbh->{CachedKids},"\n"; $dbh->{CachedKids} = {}; $dbh->do("analyze"); my $sth = $dbh->prepare_cached('select "hello" from a'); print "got ", $dbh->selectrow_array($sth), "\n";
A section of the DBI_TRACE from my main application
T <- prepare_cached('SELECT me.id FROM step me WHERE ( me.message = ? ) ' undef ...)= DBIx::ContextualFetch::st=HASH(0x8e09f38) at DBI.pm line + 381 T <- FETCH('Active')= '' at DBI.pm line 1139 T <- FETCH('Taint')= 1 at ContextualFetch.pm line 50 <- STORE('Taint' 0)= 1 at ContextualFetch.pm line 51 !! ERROR: 1 'database schema has changed(1) at dbdimp.c line 421' +(err#0) <- execute('Removing duplicates')= undef at ContextualFetch.pm lin +e 52 ERROR: 1 'database schema has changed(1) at dbdimp.c line 421' +(err#0) <> FETCH('Statement')= 'SELECT me.id FROM step me WHERE ( me.message = ? ) ' ('Statement' from cache) at DBI.pm line 1143 Val::Step can't SELECT me.id FROM step me WHERE ( me.message = ? ) : DBD::SQLite::st execute failed: database schema has changed(1) at db +dimp.c line 421 [for Statement "SELECT me.id FROM step me WHERE ( me.message = ? ) "] at /usr/share/perl5/DBIx/ContextualFetch.pm line 52. at bin/validate.pl line 196

In reply to Re: Upgraded SQLite: "database changed" error by bsb
in thread Upgraded SQLite: "database changed" error by bsb

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.