Here, check this out... https://gist.github.com/tlorens/04be0a045cab50486733
I was able to make this 'work' by setting up: <id name="serviceSurvey" association-key="true" /> <id name="symptom" association-key="true" /> In "ServiceSurveySymptom" to make the 'key' unique. Otherwise, only one row is returned when just using the serviceSurveyId On Sunday, March 2, 2014 1:13:51 PM UTC-5, Timothy Lorens wrote: > > Attached Is a sample of an association. In the past we've had issues with > children records that have the same 'key'. In this case the > SERVICE_SURVEY_ID 3905 has 3 rows. I know in the past we've had issues > with this only hydrating/populating 1 object. I've implemented an SQL > Logger to capture all the queries that are generated and the queries are > correct. Copy/Paste them into SQL Developer and get back the expected > results. We've been able to make a composite key-- say including (in this > case) SYMPTOM_ID as an ID in our XML mapping files and as long as > everything is unique, everything seems to work. > > Suggestions? And we can't put go to 120 tables and add surrogate keys to > everything. We have some table associations that don't work with Doctrine > and we've coded around this for the most part. I'd like to think this > situation is fairly common and Doctrine should be able to handle this. > > -Tim > -- You received this message because you are subscribed to the Google Groups "doctrine-user" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/doctrine-user. For more options, visit https://groups.google.com/groups/opt_out.
