relationship

Any idea how to use an include with attributes (when you need to include only specific fields of the included table) with sequelize? Currently I have this (but it doesn't work as expected): var attributes = ['id', 'name', 'bar.version', ['bar.last_modified', 'changed']]; foo.findAll({ where : where, attributes : attributes, include : [bar] }).success(function (result) { ... Something like this should work foo.findAll({ where : where, attributes : attributes, include : [{ model: bar, attributes: attributes}] }).success(function (result) { 来源： https://stackoverflow.com/questions/21883484/how-to

While doing the HTML for my new template, I stumbled across a new meta tag <link rel="profile" href="http://gmpg.org/xfn/11" /> What's this for? I found it linking to this page , and through Google I found this Microformat but I didn't get it. unor In HTML 4.01, there is the profile attribute for the head element: This attribute specifies the location of one or more meta data profiles, separated by white space. For future extensions, user agents should consider the value to be a list even though this specification only considers the first URI to be significant. It is used to link to meta data

I have 2 Entities: Categories and products. How can I build a relationship between these Entities? Category Entity: class Category { private $id; private $name; private $parent; public function getChildren() { return $this->children; } //setters and getters } Items Entity: class Items { private $id; private $name; private $price; private $color; private $size; private $weight; //getters and setters } Category yml: AppBundle\Entity\Category: type: entity oneToMany: children: targetEntity: AppBundle\Entity\Category mappedBy: parent orderBy: name: ASC manyToOne: parent: targetEntity: AppBundle

I currently have a database with two tables called Articles and Tags . In order to allow articles to be in multiple categories i have a many to many relationship. Is it a mistake to have such a design in terms of performance? or should i remove the relationship between these two table and add a third table as a bridge (articlesTags)? There's nothing inherently wrong with having a many-to-many relationship, you'll just need to create a Junction Table (which is what it sounds like you're referring to with articlesTags ) to facilitate that relationship. You're seeing the difference between a

I'm new to defining relationships and frameworks all together, I'm just used to raw SQL. Did my homework (google + Laravel documentation) but I think I'm just not understanding it properly. Heres is the relevant information: User Table: Table: Users id - int (auto increment) username - varchar Challenges Table: Table: Challenges id - int (auto increment) name - varchar User_challenge_links Table User_challenge_links id - int (auto increment) user_id - int challenge_sub_categories_id - int Challenge_sub_categories Table Challenge_sub_categories id - int (auto increment) category_id - sub

In my elastic search server I have one index http://localhost:9200/blog . The (blog) index contains multiple types. e.g.: http://localhost:9200/blog/posts , http://localhost:9200/blog/tags . In the tags type I have created more than 1000 tags and 10 posts created in posts type. e.g.: posts { "_index":"blog", "_type":"posts", "_id":"1", "_version":3, "found":true, "_source" : { "catalogId" : "1", "name" : "cricket", "url" : "http://www.wikipedia/cricket" } } e.g.: tags { "_index":"blog", "_type":"tags", "_id":"1", "_version":3, "found":true, "_source" : { "tagId" : "1", "name" : "game" } } I