On Sat, Jul 21, 2012 at 4: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.

Read the documentation carefully:
http://www.sqlite.org/fts3.html#matchinfo. Right the first paragraph:

The matchinfo function returns a blob value. If it is used within a
query that does not use the full-text index (a "query by rowid" or
"linear scan"), then the blob is zero bytes in size. Otherwise, the
blob consists of zero or more 32-bit unsigned integers in machine
byte-order.

What part of this paragraph makes you believe that if you print the
result of matchinfo as text you will see something meaningful?


Pavel
_______________________________________________
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Reply via email to