From: [EMAIL PROTECTED] on behalf of Mck
> > Should this be intelligent enough to close any parantheses or similar,
> > in case there are any open after truncating?
> > [snip]
> > This is probably not very urgent, though. Might be suitable for 2.18?
>
> Quite right. I had this in mind.
> The user does see the truncated query on the result page so it should be
> obvious was went wrong and for the user to correct.
> It can be re-addressed in 2.18 if the need comes. ok?
Obvious to you, maybe, but it gives the frontend no way of behaving user
friendly. Most users will just be annoyed, I think. If the frontend somehow
knows that this has happened it can address the issue to the user in a nice and
polite way.
The same goes for search command timeouts, etc. What if the search object
contains status information (in the field map).
E.g. {"timedout" => "true", "truncated" => "256", "unknownError" => "false",
"convertedToOr" => "true"} // These are the useful ones I can think of,
probably a lot more :-)
So it can be fetched like $datamodel.getSearch("..").getField("timedout")
If it's easy (or even possible) to send this information from the search
command to the search object I don't know. But still it'd be really useful.
--
Magne
_______________________________________________
Kernel-development mailing list
[email protected]
http://sesat.no/mailman/listinfo/kernel-development
