[yocto] [pseudo] Pseudo 1.8+ xattr sqlite corruption

[Joshua Watt]

On Tue, Sep 18, 2018, 16:09 Seebs <seebs at seebs.net> wrote:

> On Tue, 18 Sep 2018 20:26:59 +0000
> <Jack.Fewx at dell.com> wrote:
>
> > SO... any suggestions how to make the inodes in the database an
> > UNSIGNED value?
>
> We probably *can't* -- sqlite doesn't support that! They cap out at 8
> byte integer values, and are always signed. I don't know of a way to
> fix this. We might be able to trick it by coercing them into the signed
> range, and reversing the conversion later. And this is outside the
> range that's accurately representable in float, too. Whee!
>

Are the databases supposed to be shareable between different build
machines? IIRC, the answer is no. Could you store the native inode type as
a sqlite BLOB? Not necessarily a good idea.... Just an idea.


> -s
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/yocto/attachments/20180918/674ff70d/attachment.html>