ansaurus

Question

Answer 1

+1 A:

How about this:

BusinessEntityTeam:
  Nicole_Team:
    name: Nicole's Team
    Business: [ACMEWidgets]

sfGuardUser
  Nicole:
    first_name:     Nicole
    last_name:      Jones
    email_address:  [email protected]
    username:       nicole
    password:       nicole
    Groups:         [Group_abc]
    Team:           [Nicole_Team]
    ManagerFor:     [Nicole_Team]

In order to avoid circular referencing, you have to put the relations in one model.

Peter Long 2010-09-24 02:56:29

Thanks for your answer. I tried this, adding a bidirectional relationship between BusinessEntityTeam and sfGuardUser in order to have a relation to reference. The fixture loads with no error being thrown, but the value is still NULL

PeterB 2010-09-24 16:17:38

Why did you add a bidirectional relationship? What I did is to avoid such a relationship. If you want to know a team's manager, you'd have to write a method in your team model. such as function getManager() and implement the method yourself. The sql should be something like "select top 1 from user u where u.manager_for = ?"

Peter Long 2010-09-25 16:10:53

I made a mistake. You do not need to write a getManager() method yourself. And you don't need to add a bidirectional relationship either. The relationship are automatically bidirectional. For example, you add a relationship from User to Team, then you have two methods: user->getTeam() and team->getUsers() automatically. For your example: there will be two methods user->getManagedTeam() and team->getManager(). I have to read your schema.xml to tell you more detail.

Peter Long 2010-09-26 01:18:23

What you write sounds correct, but still isn't working in my case. I think this is because I have a lot of loops/references between all tables, and there's other dependencies not resolved. I'm therefore marking this as the correct answer.

PeterB 2010-09-28 09:24:15

ansaurus

tags:

views:

answers:

Doctrine fixtures - circular references

related questions