On migration abortion, print optional csv
Found this using the tool from the terminal. The migration tools require a prompt to do the migration (unless forced). If the migration was given an output destination for a database csv and the user aborts the migration, the csv is not created. See screenshot of error message attached. The database was created so it should be possible to print the optional csv before exiting. It seems a shame to miss out on getting the csv, especially since the user may want to explore the results before retrying (maybe the number of files seemed off or something).
That was the problem! Can make a csv, as long as they came from the same version. Thanks!
Oh the file_size error is probably because that particular db_path file was generated by an older version of the client, not the latest release client version and the file format has changed slightly during development. It should be stablish now for further runs going forward (although still probably intended that it be used with the same version of the client that generated it).
Yup. I tried it on multiple dbs from previous tests. I looked, again, and it seems to be creating the csv, but it only has a header. I thought it might be a path error so I put the full path to the db. In that case, I get OperationalError: no such column: file_size. I am not sure what is going on here.
I don’t think this is urgent. I’ll keep trying to figure out if there’s something I am doing wrong or if it’s a problem with the environment I’m working in (docker with basic Jupyter Lab).
Hmm, does the file at db_path file exist? That would be the error generated if the file did not exist. The db_path file should exist beyond the aborted migration run and then be usable with the above code, until it is manually deleted.
I get an error of OperationalError: no such table: migrations when I try to use the results.as_csv() function.