Integetr field showing as boolean, breaking phps writer

[Andrew McCombe <eu...@gmail.com>]

Hello

I have a field defined in schema.xml as an integer which should
contain either 0,1,2,10 or 11 values but my results documents are
showing this as either 'true' or 'false'. the majority of the half
million documents have this field as 0 or 1 but around 6,000  have it
as 2,10 or 11.  The field is stored but not indexed.

Also, I am using the PHPS responsewriter and I am finding that
unserializing the results in php fails.  I suspect that this is
because the output is defining the field as an integer but then
showing false:

 e.g,  ...;s:11:"recommended";i:false;....

Does anyone know why my field is stored as boolean when it should be an integer?

Regards
Andrew

Re: Integetr field showing as boolean, breaking phps writer

[Chris Hostetter <ho...@fucit.org>]

On Fri, 15 May 2009, Andrew McCombe wrote:

: I have a field defined in schema.xml as an integer which should
: contain either 0,1,2,10 or 11 values but my results documents are
: showing this as either 'true' or 'false'. the majority of the half
: million documents have this field as 0 or 1 but around 6,000  have it
: as 2,10 or 11.  The field is stored but not indexed.

the only thing i can think of that might explain what you are seeing is if 
you had a schema file, indexed some docs, and then changed your schema 
file.  

Other then that, i can't think of anything that would even remotley 
explain your situation ... if you can reproduce this in some way, and 
describe teh exact steps for other people to reproduce it, please file a 
bug.




-Hoss