Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p><strong>Just for the sake of completeness</strong> (and because <em>Member Expressions</em> can crash the query)</p> <p>As <a href="https://stackoverflow.com/users/1774881/existdissolve">@existdissolve</a> stated you can archive something similar (not the same!) of a wildcard with the use of a <strong><em>Member Expression</em></strong> like in your case</p> <pre><code>Ext.ComponentQuery.query('button &gt; menu &gt; menuitem{text.search("Welcome")!=-1}'); </code></pre> <p><em>This will try to perform the native JS search operation on the text property of any found menuitem. No matter if this property exist (or the method) which brings me to the main issue of Member Expressions</em></p> <p><strong>What you need to know about Member Expressions</strong></p> <p>You can use a <em>Member Expressions</em> on nearly every selector but they <strong>need</strong> to exist on that selector or you end up with a exception which aborts the query (totally, like a exception does). </p> <p>Here's a simple example. Let's say you want to find a button by it's text. That should be no problem, all buttons need a text, didn't they? This works for quite a time till your customer complains that some buttons don't need text a simple image would be enough. You have forgotten about the query thing and add the button and suddenly parts of your application stop working while you end up with a exception like</p> <blockquote> <p><em>Uncaught TypeError: Cannot call method 'search' of undefined</em></p> </blockquote> <p>You can try it yourself in this <strong><a href="http://jsfiddle.net/sran/9kPsY/" rel="nofollow noreferrer">JSFiddle</a></strong> example. Try 'find me' and after that hit the 'add image button' and try it again. </p> <p><strong>Why does this happen?</strong> The <code>Ext.ComponentQuery</code> test neither if property exist nor if the expression exist which can quickly lead to a total fail of the query.</p> <p>Yes, the example above is simple and you may find the source of the error real quick but it can also be completely different.</p> <p><strong>What now?</strong> I don't want to say to say that you should not use a <em>Member Expression</em> but you really need to care about the side effects that you may face.</p>
    singulars
    1. This table or related slice is empty.
    1. POExt ComponentQuery wildcards
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USCommunity
    1. USsra
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COAgreed. In the case of the original question, I would probably opt for putting a unique name on the type of menut item being used (regardless of the mutability of the text), and then simply use that name in the the more "standard" component query.
      singulars
      1. PO
      1. USexistdissolve
    2. CO@existdissolve Don't get me wrong. In my comment to your answer I am referring to the API not your answer. I think I didn't made that clear enough. Your answer is absolute correct. With my addition I just want to to point out the cons of `Member Expressions`
      singulars
      1. PO
      1. USsra
    3. COThanks I wanted to avoid assign ID to my components and just use generated ID. But in this case I think I'll do just that and you the simple query as @existdissolve points out.
      singulars
      1. PO
      1. UScodemonkeyww
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload