On Friday, December 6, 2002, at 01:59 PM, Lixin Meng wrote:
Sounds to me like a bug. That might be a good excuse for someone to look at the source code, and see aboud contributing a fix. (It won't be me, at least until I meet my other deadlines ;-)xindice xpath_query -c /db/testing -q "/data/[EMAIL PROTECTED] = '1']"
will get an error message:
= was unexpected at this time.
Any idea why the white space matters? Also, is there any plan for returning
attributes?
I think there is a fundamental problem with returning attributes, as they have to be attributes *of some element*
You may want to rethink your schema, (as I had to do recently) to deal with the problem.
Again, appreciate your help.
Lixin
-----Original Message----- From: Matthew Van Horn [mailto:[EMAIL PROTECTED] Sent: Thursday, December 05, 2002 7:02 PM To: [email protected] Subject: Re: XPath problem
On Friday, December 6, 2002, at 12:00 PM, Matthew Van Horn wrote:
1. Xindice will NOT return attributes, only elements. xindice xpath_query -c /db/testing -q /data/test2/forTest2 **will not work
2. use quotes around your query when using the command line, otherwise the shell tends to screw things up - especially with quote and parentheses characters. It's easier to use quotes than to escape everything that needs to be escaped. xindice xpath_query -c /db/testing -q "/data/test2[forTest2 = '1']"
and I forgot - the query should be: "/data/[EMAIL PROTECTED] = '1']" ^denotes attribute
