Raj Kumar wrote:
> hi dirk,
> Do you have any idea about the string format of the end user code on the
> client side
> that is used to generate the xml for the basic search format or other
> such formats.
> thanks,
> rajkumar
Hi Raj
Depends on kind of search of course, for the basicsearch I think that the
programmer would directly write the xml. Maybe we could offer him the same
functionality as the sql package does with preparedstatement, allowing him to
bind variables.
For the command line client I would give the normal sql syntax to the end user
and not the xml variant, maybe we can offer this syntax to the programmer too.
In earlier mails you said something about a BasicseachQuery class to encapsulate
the query maybe that class can be used on the client as well. You could compose
your query by adding "where",... nodes to your search object.
I have experimented with sutch an interface before including a nice gui on that
but in the end the novice users preferred a simpler full-text search and the
experts didn't want a gui but a text box in which they copy/pasted their
queries.
But now most programmers/experts are used to building xml trees so building a
seach out of search building bloks is not that strange anymore.
Do you already have some code/ideas on that BasicseachQuery class ?
Dirk
