However, when I tried to run this last summer, only ASCII output worked. There was a discussion on Slack at the time (See August 7, 2018 and subsequent in #queries). The initial indications were that the ordering of SQL commands in the binary output may have been a factor, especially when used with --truncate. I can't find a record of any other bug report, so now I'm creating one.
Various documents say that
fits2db
should produce binary output. For example, this snippet from the "ingest party" tutorial.However, when I tried to run this last summer, only ASCII output worked. There was a discussion on Slack at the time (See August 7, 2018 and subsequent in
#queries
). The initial indications were that the ordering of SQL commands in the binary output may have been a factor, especially when used with--truncate
. I can't find a record of any other bug report, so now I'm creating one.