Skip Menu |

This queue is for tickets about the Search-QueryParser CPAN distribution.

Report information
The Basics
Id: 47423
Status: resolved
Priority: 0/
Queue: Search-QueryParser

People
Owner: Nobody in particular
Requestors: slagelwa [...] yahoo.com
Cc:
AdminCc:

Bug Information
Severity: (no value)
Broken in: (no value)
Fixed in: (no value)



Subject: Quoting both the field name and the value
Hi, I have a quick question (or bug?) What is suppose to happen when you quote both the field name and the value? For example, Show quoted text
LastEdit>"2009-01-01" parses as LastEdit>"2009-05-17"
"LastEdit">"2009-01-01" parses as :"Last Edit" :>"2009-05-17" which implies that quoting the field name is something you shouldn't be doing as it then treats it as just another value. Problem is that there isn't any error/indication from the parser telling you that the query is formatted incorrectly (well, at least in its interpretation of what you want it to do). Thanks
Le Dim. Jun. 28 21:05:19 2009, JSLAGEL a écrit : Show quoted text
> Hi, > > I have a quick question (or bug?) What is suppose to happen when you > quote both the field name and the value? > > For example, >
> LastEdit>"2009-01-01" parses as LastEdit>"2009-05-17"
> "LastEdit">"2009-01-01" parses as :"Last Edit" :>"2009-05-17" > > which implies that quoting the field name is something you shouldn't be > doing as it then treats it as just another value. Problem is that there > isn't any error/indication from the parser telling you that the query is > formatted incorrectly (well, at least in its interpretation of what you > want it to do). > > Thanks
Hi, Currently there is no builtin support for quoting field names. That would be probably a good thing to add, so I'll include it in a next release. Meanwhile, you can always use the 'rxField' parameter to customize fields according to your needs, supplying the appropriate regex. Cheers, Laurent D.
Solved in 0.94, just posted to CPAN