3

The interesting tag [ejb*] (<- that's a link) should match [ejb] and [ejb3] but does only match [ejb].

The interesting tag [jee*] (<- that's a link) should match [jee5] and [jee6] but doesn't match anything.

The interesting tag [hbm*] (<- that's a link) should match [hbm], [hbm2java], [hbm2ddl] but does only match [hbm].

Update: Actually, this question seems to be a [status-bydesign] candidate: wildcards requests use 4 characters at least (or the wildcard appear to be ignored). This would explain the mentioned behavior. Is there a previous question that confirms this rule? I couldn't find one.

3 Answers 3

3

The syntax for client-side JavaScript wildcard tag matching uses *.

The syntax for server-side SQL wildcard tag matching uses ~. On the server side we restrict this to minimum 4 character matches to prevent too much explosion in matches.

1
  • I'll take that as authoritative answer :) Commented May 29, 2010 at 21:37
2

The star is ignored; use tilde (~) as a wildcard. (You have to use at least 4 characters, apparently, so ejb~ won't work.)

2
  • On second reading, are you talking about interesting tags as displayed on the homepage instead of searching? If so, I'll delete this.
    – Gnome
    Commented May 29, 2010 at 17:35
  • As displayed (my question includes the corresponding server side requests with tilde). However, the 4 characters rules seems to be the explanation. Is it a publicly known rule? Anyway, I think I'll accept this answer but maybe you could rephrase (remove?) the beginning. Commented May 29, 2010 at 20:34
1

Try ej[b]~, je[e]~, hb[m]~. Basically work-around for those with numbers.

1
  • Thanks. This works indeed, but it seems I can't use this syntax in interesting tags. Commented May 29, 2010 at 20:16

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .