On Fri, Aug 17, 2018 at 5:14 AM Tim Streater <t...@clothears.org.uk> wrote:
> On 17 Aug 2018, at 01:24, Casey Rodarmor <ca...@rodarmor.com> wrote: > > > I wrote an erroneous update statement: > > > > ``` > > UPDATE foo SET bar = x'01234'; > > ``` > > > > The error message was: > > > > ``` > > unrecognized token: "x'01234' > > ``` > > > > *I know now *that the problem was that the blob's length was not a > > multiple of two. However, the error message didn't give me an > > indication of that. Would it be possible to make the error message > > more explicit, to help users debug this error? > > I expect the error message is correct, and that what you meant to write > was: > > while 'correct' it's not meaningful is what the OP meant, I beleive. something like bad encoding: "x'01234' would be much more meaningful(?) > update foo set bar = 0x1234; > > > See: > > <https://www.sqlite.org/lang_expr.html> > > and scroll down to the part about Literal Values (Constants). > > > > > -- > Cheers -- Tim > _______________________________________________ > sqlite-users mailing list > sqlite-users@mailinglists.sqlite.org > http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users > _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
