one-to-many

I'm quite new to Laravel. I'm figuring out to work with Eloquent. Let's say I have 2 tables: categories and products. These two table have a one-to-many relationship. 1 category can have many products. I would like to return a JSON response which consists of an array of categories where each category has an array of products. It should look like this: [ {"name":"Category 1", "products": [ {"name":"Product 1","price":"2.50"}, {"name":"Product 2","price":"2.50"} ] }, {"name":"Category 2", "products": [ {"name":"Product 1","price":"1.95"}, {"name":"Product 2","price":"2.15"} ] } ] Models:

I am using spring 4.1.4.RELEASE + hibernate 4.3.6.Final, here is my entity code: public class BaseEntity implements Serializable { } public class MarketInfo extends BaseEntity { @Id @GeneratedValue(strategy = GenerationType.AUTO) @Column(name = "id") private int id; @Column(name = "market_id", unique = true, length = 15) private String marketId; @OneToMany(fetch = FetchType.LAZY, mappedBy = "market") private List<MarketChannelGroup> channelGroups; public List<MarketChannelGroup> getChannelGroups() { return channelGroups; } public void setChannelGroups(List<MarketChannelGroup> channelGroups) {

This question is related to my another question: Doctrine2 gives me only first instance of related objects I came up with bidirectional association to try solve my old issue but now I have another problem. Schema [EDITED] : XYZ\Bundle\CitiesBundle\Entity\Cities: type: entity table: cities fields: id: id: true type: integer unsigned: false nullable: false generator: strategy: IDENTITY name: type: string length: 50 fixed: false nullable: false landarea: type: decimal nullable: false density: type: integer unsigned: false nullable: false population: type: integer unsigned: false nullable: false

I've got a Hibernate entity, called Event, which has a one-to-many metadata entity, EventData. Given the following Event: EventId: 1 EventHash: broccoli With the following EventDatas: EventDataId: 1 EventId:1 Field: tag Content: tagme EventDataId: 2 EventId: 1 Field: tag Content: anotherTag How do I create a Criteria query to retrieve the event which has BOTH tags "anotherTag" and "tagme"? In SQL, I'd join the event_data table once for each tag being searched for, but I can only seem to create one alias for the Event.EventData relationship, i.e. int inc = 0; Conjunction junc = Restrictions

I thought a query like this would be pretty easy because of the nature of relational databases but it seems to be giving me a fit. I also searched around but found nothing that really helped. Here's the situation: Let's say I have a simple relationship for products and product tags. This is a one-to-many relationship, so we could have the following: productid | tag ======================== 1 | Car 1 | Black 1 | Ford 2 | Car 2 | Red 2 | Ford 3 | Car 3 | Black 3 | Lexus 4 | Motorcycle 4 | Black 5 | Skateboard 5 | Black 6 | Skateboard 6 | Green What's the most efficient way to query for all (Ford

I have tried to search online for a definite solution to this question but there's really no concrete solution for newbies out there. I have an Entry which has many EntryListing. In my EntryAdmin listMapper, i comfortably can list entries by a statement as simple as ->add('listings') which simply returns the listings as defined in the EntryListing __toString() function. Is there a way to achieve the same when exporting the data by overiding the getExportFields() functions as below: public function getExportFields() { return array('name','tel','email','deviceType','postedOn','createdAt',

Typical usage scenario: I have master, branch_foo and branch_bar. All are up to date. Now, I do a "git checkout master" and work on a bug fix. Lets say that fix was on a tracked file that is in the same state on all branches - ie. before the fix, a diff of the file from each branch results in no differences. Is there a way to commit this fix to all branches? Tim Henigan I expect git cherry-pick is what you want. After committing the fix to the first branch, you can use git cherry-pick to merge it into each of the other branches. This related question on SO may be of interest: Git & Working on