Hm, FTS internally may operate with text data only and so blob/text
types are equal. In my compression patches for FTS the blob result of
uncompress() is correct... but there is no documentation for FTS4
compression and will be type ignoring of uncompressed values correct
in future? Saving types
On 04/13/2011 02:49 PM, Alexey Pechnikov wrote:
> What type of value return _uncompress_? The original content may be
> blob or text, so uncompress may return blob I think... Or we need to
> store in compressed field the type of this.
I guess that is correct. uncompress() should return the same
What type of value return _uncompress_? The original content may be
blob or text, so uncompress may return blob I think... Or we need to
store in compressed field the type of this.
The compression does not work for indices?! But FTS index compression
can reduce indices size by factor 3x-4x...
On 04/13/2011 06:22 AM, Alexey Pechnikov wrote:
> Which functions will be correct? As example, affinity for uncompress
> functions can be as "blob" as "text". Now this is not important but
> some tests will be nice for future compability.
You mean what type of value should compress() return?
Any
Which functions will be correct? As example, affinity for uncompress
functions can be as "blob" as "text". Now this is not important but
some tests will be nice for future compability.
--
Best regards, Alexey Pechnikov.
http://pechnikov.tel/
___
5 matches
Mail list logo
