nested

I have a MySQL table. Let's call it Widgets. The Widget table has 3 fields: id , type_id , and name . I want, in one query, to get all the widgets that share a type_id with the Widget named 'doodad'. I've written 2 queries: Give me the type_id of the widget with the name 'doodad'. Give me all widgets with that type_id. This works. Each query, independently achieves its goal. But when I combine them into a single nested query, it runs forever, infinite loop style. It looks like this: SELECT * FROM widgets WHERE type_id IN ( SELECT type_id FROM widgets WHERE name = 'doodad' ); Can anyone explain

I came up with this question when I was trying to answer this . The following is an expected behaviour: module A p Module.nesting end # => [A] But the following: A.instance_eval{p Module.nesting} A.instance_exec{p Module.nesting} A.module_eval{p Module.nesting} A.module_exec{p Module.nesting} all return [] . Why do these not work as the above? Additional Question Mu is too short suggested an interesting point. If that is correct, then Module.nesting would be one of the methods and variables that are dependent on the literal context like Method#source_location , __FILE__ . Is this understanding

I have this small gridComponent: @Component({ selector: 'moving-grid', templateUrl: './grid.component.html', styleUrls: ['./grid.component.css'] }) export class GridComponent { @Input('widgets') extComponents: Array<Component>; } And a second testComponent @Component({ selector: 'test', template: ` <div #content>I say hello<li>i</li><li>u</li><button (click)="test()">click me</button> world</div> ` }) export class TestComponent { @ViewChild('content') content: HTMLElement; getContent() { return this.content; } test() { console.log("test"); } } Now I'm trying to pass multiple instances of

I have trouble combining term, must_not queries on nested documents. Sense example can be found here : http://sense.qbox.io/gist/be436a1ffa01e4630a964f48b2d5b3a1ef5fa176 Here my mapping : { "mappings": { "docs" : { "properties": { "tags" : { "type": "nested", "properties" : { "type": { "type": "string", "index": "not_analyzed" } } }, "label" : { "type": "string" } } } } } with two documents in this index : { "tags" : [ {"type" : "POST"}, {"type" : "DELETE"} ], "label" : "item 1" }, { "tags" : [ {"type" : "POST"} ], "label" : "item 2" } When I query this index like this : { "query": { "nested":

I just started using git and started collaborating with other developers on same code. I have worked a little with SVN before but never had to collaborate with other people on my codebase. Now with collaborators working on same code, I need an efficient workflow. While searching for such, I found this , and it seems like a good workflow for our requirement. My repository resides in a local machine. I created the repository with git init --bare . I added the initial codes to master and pushed it. Then I added a "develop" branch using git branch develop; git push -u origin develop . Now I want

I have some dictionaries of dictionaries, like this: a['b']['c']['d']['answer'] = answer1 a['b']['c']['e']['answer'] = answer2 a['b']['c']['f']['answer'] = answer3 .... a['b']['c']['d']['conf'] = conf1 a['b']['c']['e']['conf'] = conf2 a['b']['c']['f']['conf'] = conf3 Is there a fast way to get a list of values of all answers for all elements at the third level (d,e,f)? Specifically I'd like to know if there's any mechanism implementing a wildcard (e.g., a['b']['c']['*']['answer'].values() update The fastest way I've found till now is: [x['answer'] for x in a['b']['c'].values()] Richard In