ports/162650: sqlite3 command shell incorrectly handles some blobs

[Pavel Volkov]

I completely agree with you.
You have already reported the problem and the solution to the mailing
list sqlite-dev?
We can use the patch as a temporary solution.

http://www.sqlite.org/src/tktview?name=72adc99de9
http://www.sqlite.org/src/info/a2ad9e6363

FreeBSD ***.*****.ru 9.0-RC2 FreeBSD 9.0-RC2 #0: Fri Nov 11 12:05:44
MSK 2011     root@***.*****.ru:/usr/obj/usr/src/sys/ext  amd64

SQLite version 3.7.9 2011-11-01 00:52:41
Enter ".help" for instructions
Enter SQL statements terminated with a ";"
sqlite> .mode insert
sqlite> select X'79';
INSERT INTO table VALUES(X'79');
sqlite> select X'80';
INSERT INTO table VALUES(X'ffffff80');


On Thu, Dec 22, 2011 at 15:23, Ruslan Mahmatkhanov <cvs-src at yandex.ru> wrote:
>
> Pavel Volkov wrote on 22.12.2011 14:10:
> >  Hello. You are right. I applaud your patch. I also request to increase
> >  PORTREVISION. Thank you.
>
> I still insist that this is upstream issue, because, as i wrote to
> Valentin in private email, i'm able to reproduce this in CentOS/RHEL 6.0
> with stock sqlite 3.6.20. So this is actually should be reported upstream.
>
> I'll commit this later this day after yet another testing.
>
> --
> Regards,
> Ruslan
>
> Tinderboxing kills... the drives.