-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Florian Weimer wrote: > I think you can do this with BLOBs.
Of course, but INTEGERs are automatically converted in a .dump ;-) > | BLOB literals are string literals containing hexadecimal data Oh, I *really* didn't notice they were represented as an hex format. > Unfortunately, the sqlite3 command line client does not seem to be > able to output BLOB fields in a readable way. But this could probably > be fixed upstream. C:\cygwin\home\lapo>sqlite3 prova SQLite version 3.0.8 Enter ".help" for instructions sqlite> CREATE TABLE a(b); sqlite> INSERT INTO a VALUES (X'1200AB'); sqlite> .dump BEGIN TRANSACTION; CREATE TABLE a(b); INSERT INTO "a" VALUES(X'1200AB'); COMMIT; It probably already has (even in the now old 3.0.8 it does it), in that case I guess the point about dump/import being "diffuclt" with BLOBs should be moot, shouldn't it? (the fact that dumps would be twice the size of the DB is less important IMHO than using base64 all around...) - -- L a p o L u c h i n i l a p o @ l a p o . i t w w w . l a p o . i t / -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (Cygwin) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iEYEARECAAYFAkMy2qQACgkQaJiCLMjyUvu8iQCcD6APEdzbXKW7PMj3P4wocLjc ZyQAniiq59FAQr7VZXTkL7HoWZ0hpnh0 =pA3H -----END PGP SIGNATURE----- _______________________________________________ Monotone-devel mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/monotone-devel
