Sorry, almost missed this one. I thought WeeWX used a vacuum somewhere but it seems not. (it was discussed when we were working on a database patch a couple of years back and I am aware of a couple of extensions that insert/delete data in some secondary databases that use it via schedule). I had it in my mind the adding/deleting caused the bloat whereas adding only (as wee_import does) does not.
I guess you did in fact do a vacuum, did it bring the size down? Happy to look at implementing it somehow if there is a demonstrated benefit. Gary On Friday, 14 August 2020 10:37:27 UTC+10, Ryan Stasel wrote: > > So, did get it working. Interesting note. When I was previously doing > imports from a WC exported csv, my weewx.sdb, after import, was about 160MB > (10 years of data). After importing from weewx, my weewx.sdb is over 600MB. > > Would there be any benefit to a VACUUM on sqlite post import? not entirely > sure what would be taking up all the extra space. > > On Monday, August 3, 2020 at 8:28:39 PM UTC-7, gjr80 wrote: >> >> On second thoughts there probably is some scope to have some sort of >> ignore list. I can see it relying on the user having a reasonable >> understanding of his/her data. I will make a note to look at this again. >> >> Gary >> >> On Tuesday, 4 August 2020 10:33:18 UTC+10, Ryan Stasel wrote: >>> >>> Cool! It just was hard to track what was going on given the >>> errors/warnings. >>> >>> Shame we can't just say ignore those (fields, or lack there of) during >>> import, unless I'm missing something obvious. >>> >> -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/4060762d-dd86-442c-9634-b08bab1a7c4ao%40googlegroups.com.
