In that case, just work in mysql directly - it is generally more versatile than sqlite3.
I see no benefit in transferring to sqlite3 as an intermediate, I was just assuming that was where your data was stored. It goes without saying that you back up your db before embarking on this. On Thursday, 17 October 2019 11:19:19 UTC+10, Pat wrote: > > This is great! > > I use MySQL primarily as my source, but frequently flip/flop for testing > various things. I can export the 20,000 rows to SQLite, run this then > import the new rows back to MySQL. Thanks! > > > -- You received this message because you are subscribed to the Google Groups "weewx-development" 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-development/01c2192a-b6ce-457a-ab9a-227149edc66a%40googlegroups.com.
