found my own failure ;-) the scope in xpath must be "." not "*"
//element(*, nt:base)[jcr:contains(., '*.txt')] works now BR, claus -----Ursprüngliche Nachricht----- Von: KÖLL Claus [mailto:[EMAIL PROTECTED] Gesendet: Donnerstag, 05. April 2007 07:10 An: [email protected] Betreff: AW: Strange behaviour between sql and xpath search hi brian, thank you for the hint, but i want to find the name through the fulltext search .. the users are searching in the fulltext and should also be able to find a document not only by its content but also with its name so *.txt is a valid search in my case claus -----Ursprüngliche Nachricht----- Von: Brian Thompson [mailto:[EMAIL PROTECTED] Gesendet: Donnerstag, 05. April 2007 01:52 An: [email protected] Betreff: Re: Strange behaviour between sql and xpath search Try SELECT * FROM nt:base WHERE my:name = 'test.txt' or something like SELECT * FROM nt:base WHERE contains(my:name, '%.txt') -Brian On 4/4/07, KÖLL Claus <[EMAIL PROTECTED]> wrote: > > yet another information, > > the "test.txt" string is in the my:name property . > the file node name itself is something like "hgugh2374jbbjk.txt" > > claus > -----Ursprüngliche Nachricht----- > Von: KÖLL Claus [mailto:[EMAIL PROTECTED] > Gesendet: Mittwoch, 04. April 2007 17:29 > An: [email protected] > Betreff: Strange behaviour between sql and xpath search > > i have added a text file to my workspace and i would search it by its name > with the contains function > With the sql search it will be found > > SELECT * FROM nt:base WHERE contains(*, '*.txt') > > If i try to search with XPath i didnt find it ! > > //element(*, nt:base)[jcr:contains(*, '*.txt')] > > I think the two statements are the same or not ? > > With xpath i do only find strings with contains(*) on the jcr:content node > ! > Is this a bug ?? > > My node structure looks like: > > /test.txt (nt:file) > -my:name (Mixin) > - .. some Mixin properties > /jcr:content (nt:resource) > -jcr:mimetype > -jcr:lastModified > -jcr:data > > thanks for any help > claus > >
