Open jtniehof opened 2 years ago
output_interface_version
is a funny one. In process it was meant to be the output number, in the inspector I think it was there to make sure that the inspector only found the right version. But my memory is a bit fuzzy.
That's what I was wondering, if output_interface_version
was there to support us having different inspectors based on the API version. It's a funny name in the inspector context, of course.
Another one from #102. The
output_interface_version
column ofinspector
is weird. Inspectors shouldn't have output versions. This should be figured out...maybe we do nothing with it, and it's another database update. Similarly it doesn't look like we usenewest_version
. These might be from originally treating inspectors "exactly like" codes. This needs to be figured out, documented, and maybe a database update rolled out.OS, Python version, and dependency version information:
Version of dbprocessing
102 , i.e. 1d5a938ed6666e4da3069d13707f57db650715e7 or jtniehof/dbprocessing:document_tables
Closure condition
This issue should be closed when appropriate documentation describing this functionality (not just the column) is merged, and/or removing the columns from the database (with appropriate migration support.)