Just an extra note about SQLite3 and MySQL: I am running many small dB using both SQLite3 and MySQL and find both useful and equally easy to use. MySQL is definitely more complex to start with, but provides also much more flexibility than SQLite3. Administration of MySQL is essentially zero. One small but important difference in dump files is that SQLite3 starts with creating the database, while MySQL erase it before creating the new one. So if you were running MySQL, you must first edit manually the file, removing both DROP and CREATE lines before reloading the "old' file, while with SQLite3 just remove the CREATE line as you did. Enjoy and take care! Paul
Le Saturday, October 24, 2020 à 1:47:44 PM UTC+2, howe...@gmail.com a écrit : > > It worked! Thanks so much for all your help. > > Lynda > On Friday, October 23, 2020 at 10:52:55 PM UTC-4 howe...@gmail.com wrote: > >> That's what I would have thought, but old + new is what wasn't working >> because of the missing tables. That's why I was confirming that you were >> just suggesting new + old instead. >> >> But thanks to your advice about PYTHONPATH I was able to get the python >> approach to run, and we'll see if that fixes it. >> >> Lynda. >> >> On Friday, October 23, 2020 at 6:49:54 PM UTC-4 vince wrote: >> >>> On Friday, October 23, 2020 at 2:31:44 PM UTC-7, howe...@gmail.com >>> wrote: >>>> >>>> So you're suggesting dump/insert the converted old records into the >>>> smaller new file, rather than the new records into the converted old file? >>>> >>>> I can try that. Thanks! >>>> >>>>> >>>>> >>> It doesn't matter if 1+4 = 5 or 4+1 = 5 as long as your total is 5 :-) >>> >>> >> -- 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 weewx-user+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/051b9785-de3a-4b0a-8d90-d06d693a3632n%40googlegroups.com.
