complaint
lists (methinks they might live at cpan and or debian linux sites).
but as i recall the update script altered some database tables and
changed
a version variable that bc uses to tickle the 'run update_bc' message.
(version tuple in beancounter table).
since sqlite was added to bc well after the need for database table
changes
was known the original sqlite setup schema was already correct. but i
think
the variable update is still needed ... so long as you ran the script
once
things should be ok.
the larger problem i found with stock bc on postgresql (a very long
time ago)
was when beancounter is initially setup and updated via scripts the
types for
volume and ave_volume (stockprices, stockinfo) are integer. this type
is too
small to hold large volume days for indexes like nasdaq 100 or dow 30
back in
the day when trading volumes were larger.
you might want to check that the sqlite type used for these tuples is
sufficiently large enough. for postgresql i'm using bigint. this may
have been factored into more recent versions ...