GNU bug report logs - #54591
29.0.50; sqlite-select returns blob result as multibyte string

Previous Next

Full log

Message #50 received at 54591 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Lars Ingebrigtsen <larsi <at> gnus.org>
Cc: 54591 <at> debbugs.gnu.org, fjas <at> grdm.no
Subject: Re: bug#54591: 29.0.50; sqlite-select returns blob result as
 multibyte string
Date: Sat, 02 Apr 2022 17:22:54 +0300

> From: Lars Ingebrigtsen <larsi <at> gnus.org>
> Cc: fjas <at> grdm.no,  54591 <at> debbugs.gnu.org
> Date: Sat, 02 Apr 2022 15:59:28 +0200
> 
> Eli Zaretskii <eliz <at> gnu.org> writes:
> 
> > We could store unibyte strings as BLOBs, couldn't we?
> 
> As I've said, we don't know whether a column is a TEXT or a BLOB column.

When storing? we could ask the caller to specify that, or
automatically consider unibyte non-ASCII strings as BLOBs.

> And "store as BLOB" has no particular meaning -- internally in sqlite,
> there is no particular difference: Both are just a series of bytes, and
> you can put any bytes you want into the columns.

Of course; the question is how those bytes are interpreted.  The
Python examples shown up-thread show the way, I think.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.