Specifically: -- The next set of three integers (0 1 1) pertain to the hits for "default" -- in column 1 of the table (0 in this row, 1 in all rows, spread across -- 1 rows). -- SELECT matchinfo(t1) FROM t1 WHERE t1 MATCH 'default transaction "these semantics"';
-- the blob appears as an empty string. To view an ascii representation, use hex() SELECT hex(matchinfo(t1)) FROM t1 WHERE t1 MATCH 'default transaction "these semantics"'; 03000000020000000100000003000000020000000000000001000000010000001000000020000000200000000000000010000000100000000000000000000000000000010000000100000001000000 AJ ONeal On Sat, Jul 21, 2012 at 2:06 PM, AJ ONeal <coola...@gmail.com> wrote: > > Now I see a number which matches my expectations: >> > SELECT hex(matchinfo(t1)) FROM t1 WHERE t1 MATCH 'default transaction >> > "these semantics"'; >> > >> > >> 0300000002000000010000000300000002000000000000000100000001000000010000000200000002000000000000000100000001000000000000000000000000000000010000000100000001000000 >> > >> > Will you update the documentation with this information? >> > >> >> What information do you propose to add to the documentation? > > > That in order to see the data the hex() function must be used. > > I imagine that most users who are following this documentation for the > first time are using the sqlite3 binary and following along by copying and > pasting the examples. > > AJ ONeal > _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
