jecxz112 wrote:
jecxz112 wrote:After recently getting started on the financial stuff and finding GT folks were using beancounter for some data acquisition, I tried to make beancounter 0.8.8 run under Windows (using sqlite3) and after a fair bit of fiddling succeeded - up to a point.This may no longer be an issue; I have been able to create the sqlite DB with setup_beancounter properly and beancounter no longer asks me to run update_beancounter.When I run it now, I tells me I must run update_beancounter, but from all I can see, despite the claims on the beancounter site, update_beancounter has no sqlite support - unless it is implicit somehow.Is anyone else running update_beancounter under Windows with sqlite. - and if so, what is the secret,short of writing my own SQLite support into update_beancounter? TIA:-)
aloha jecxz112 you might want to post your original issue to dirk directly "Dirk Eddelbuettel" <edd AT debian.org> and or to the beancounter (bc) 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 ... ras