I suspect your problems started when you didn't specify the correct path to the sqlite file. If one does
sqlite3 foobar.sdb and foobar.sdb does not exist, sqlite3 will create an empty one. Hence the symptoms you described. Look around your file system for the "real" weewx.sdb. It looks like you used the setup.py install method, so you probably want echo ".dump archive" | sqlite3 /home/weewx/archive/weewx.sdb > /home/weewx/archive/weewx.sql -tk On Tue, Jan 9, 2018 at 5:17 AM, Cycle London <cycle.london...@gmail.com> wrote: > My weather station has been running well for almost a week. I love it. > Massive kudos to Thomas, this is a really cool piece of software. > > So I'm sitting bored in the office, and I think, 'Why not move to > MySQL?'. I have a 'test/dev' server on my LAN running 5.1.73, but although > I call it 'test/dev', it's been up for years now, and is probably as > permanent as our production box. > > Right, so I hit the Wiki, and find this article.. > > https://github.com/weewx/weewx/wiki/Transfer%20from%20sqlite%20to%20MySQL > > First command: > > echo ".dump archive" | sqlite3 weewx.sdb > weewx.sql > > I get 'sqlite3: command not found'. > > OK, so that's not a problem - I install it. It does strike me as curious > that it's not found, since I thought that weewx actually ran on sqlite? No > matter. Installed, I try again. Cool, it works! I wonder idly what's > actually in the SQL file, so.. > > root@weather:~# cat weewx.sql > PRAGMA foreign_keys=OFF; > BEGIN TRANSACTION; > COMMIT; > > Is that it ? Oh, wait. There's an sdb file in there, too. That's where > all the interesting stuff will be... > > root@weather:~# cat weewx.sdb > root@weather:~# > > Maybe not. Maybe it's some sqlite thing that I don't know about, since > although I got MySQL DBA certification about five years ago, I've not > really used it since, and have no idea about sqlite. > > Let's try the second method. My weewx.conf has this: > > [dest_binding]] > database = archive_mysql > table_name = archive > manager = weewx.wxmanager.WXDaySummaryManager > schema = schemas.wview.schema > > Let's try wee-database dry run.. > > root@weather:/home/weewx# pwd && bin/wee_database --transfer > --dest-binding=dest_binding --dry-run > /home/weewx > Traceback (most recent call last): > File "bin/wee_database", line 793, in <module> > main() > File "bin/wee_database", line 133, in main > config_path, config_dict = weecfg.read_config(options.config_path, > args) > File "/home/weewx/bin/weecfg/__init__.py", line 223, in read_config > config_dict = configobj.ConfigObj(config_path, file_error=True) > File "/usr/lib/python2.7/dist-packages/configobj.py", line 1229, in > __init__ > self._load(infile, configspec) > File "/usr/lib/python2.7/dist-packages/configobj.py", line 1318, in > _load > raise error > configobj.ConfigObjError: Parsing failed with several errors. > First error at line 356. > > Back to python errors, and I'm stumped. > > -- > 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. > For more options, visit https://groups.google.com/d/optout. > -- 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. For more options, visit https://groups.google.com/d/optout.
