I used sqlite3 python module, and it is parsed fine On Mon, Nov 28, 2022 at 9:46 PM Yauheni Pervenenka < yauheni.pervene...@viber.com> wrote:
> Christian, thanks for your effort, db was simplified for test, is it > possible to fix it on the client side? Any ideas, why is column considered > as SQLITE_TEXT if it is BLOB? > > On Mon, Nov 28, 2022 at 9:40 PM Christian Ehrlicher <ch.ehrlic...@gmx.de> > wrote: > >> >> Am 28.11.2022 um 19:16 schrieb Yauheni Pervenenka via Interest: >> > Thiago, hello, thanks for your reply, sorry have no instructions for >> > create and insert, but have data base with one value which can't be >> > parsed correct(db is cut to one value for provide example) >> > >> > https://bugreports.qt.io/browse/QTBUG-108992 >> > >> Your database looks strange to me - even though your column type >> according to the schema is BLOB: >> >> sqlite> .schema >> CREATE TABLE IF NOT EXISTS "test" ( >> "value" BLOB NOT NULL >> ); >> >> the return value of sqlite3_column_type() is SQLITE_TEXT (3). >> >> Therefore the return value is treated as string and the data is screwed >> up. If I change the return value to SQLITE_BLOB (4) in the debugger, all >> is correct: >> >> qDebug() << value.toByteArray().toHex(); >> >> --> >> >> "763130492d46ab4c9c7bb0e9789b29c3ab1e4723dea6c8e5d2f9b266a275e1fbe4a6" >> >> >> >> Christian >> >>
_______________________________________________ Interest mailing list Interest@qt-project.org https://lists.qt-project.org/listinfo/interest
