Hi Dmitry,
According to the documentation, attribute types include unsigned
integers only. (There are other attribute type options, such as
floating point and string values, but the UpdateAttributes API appears
to only support 32-bit values; I use the PHP API as a reference for the
perl implementation).
http://sphinxsearch.com/docs/2.0.4/attributes.html
Regards,
--
Jon Schutz
CTO, YourAmigo Ltd
53 Gilbert St
Adelaide SA 5000
Ph: +61 8 82119211
Fax: +61 8 8211 6356
http://www.youramigo.com
On 13/05/12 23:59, Dmitry Dedukhin via RT wrote:
Show quoted text> Sun May 13 10:29:09 2012: Request 77178 was acted upon.
> Transaction: Ticket created by Demetros
> Queue: Sphinx-Search
> Subject: UpdateAttributes and negative values
> Broken in: (no value)
> Severity: (no value)
> Owner: Nobody
> Requestors: dedukhin@mail.ru
> Status: new
> Ticket <URL:
https://rt.cpan.org/Ticket/Display.html?id=77178 >
>
>
> Is there any reason why I can't set negative value using UpdateAttributes
> API call?
> The code that prevents this:
>
> else {
> croak("entry value $v is not an integer") unless ($v =~
> /^(\d+)$/o);
> }
>
> I think regexp should be changed to /^(-?\d+)$/o
