2019-11-23, 18:13
I for one was happily oblivious.
Can you share the data that the GetAlbumsByWhereJSON call would have returned by running the query (listed in the debug) in a SQLite browser, hoping that you still have the same library available. Seeing the data, or some idea of where the offening byte was in the JSON data will help me get my head around it better.
GetAlbumsByWhereJSON builds the JSON results as a variant array, but nothing to ensure valid utf-8 byte is done. I don't think anywhere else checks it either.
Is this a Python 3 thing compared to Python 2? If so then the answer may lie in the Python interface side of things rather than when the JSON is created
Can you share the data that the GetAlbumsByWhereJSON call would have returned by running the query (listed in the debug) in a SQLite browser, hoping that you still have the same library available. Seeing the data, or some idea of where the offening byte was in the JSON data will help me get my head around it better.
GetAlbumsByWhereJSON builds the JSON results as a variant array, but nothing to ensure valid utf-8 byte is done. I don't think anywhere else checks it either.
Is this a Python 3 thing compared to Python 2? If so then the answer may lie in the Python interface side of things rather than when the JSON is created
