could be happening :
1)It's a really stupid question, since the entire approach is wrong, and you need to RTFM
2)It's a known problem, with no solution, RTFM and you'll see it in the archives
Well the archives have several threads about it, but no solution is evident, so I suppose it's just an issue with Xindice.
It seems a no-brainer in terms of dealing with any reasonable DB to have some kind of server side cursor to solve such problems.
Guess I'll have to dust off my coding jacket, and get involved in the project.
Cheers.
[EMAIL PROTECTED] wrote:
Is it possible to specify a limit to the # results returned by an XPath query?
I have a DB with about 500 smallish documents in it, and applying an XPath expression to some frequently occuring attributes
keeps giving me an out of memory exception at the point :
ResourceSet resultSet = service.query(xpathString);
A second question, is it possible to have these results sorted by a given attribute found in the ResultSet, or do I need to apply a
seperate XSLT to the result set to do this.
Many thanks for any assistance.
WH
