Which means every table needs to have a surrogate ID which to a lot of DBA's is bad practice for children/associations.
It's a fairly simple concept to have a COMMENT associated with a POST. Why a COMMENT_ID is required just to make it 'unique' is beyond me and the team. I'm sure I'm beating a dead horse and this isn't the first time you've had to express this thought/idea. Thanks for your time. On Monday, March 3, 2014 4:25:41 PM UTC-5, Marco Pivetta wrote: > > > On 3 March 2014 19:58, Timothy Lorens <[email protected] <javascript:>>wrote: > >> 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 >> >> > Right, so your previously set PK wasn't unique :-) > > That's not really something borked at ORM level - you are required to have > a unique key that "identifies" an entity. > > Marco Pivetta > > http://twitter.com/Ocramius > > http://ocramius.github.com/ > > > -- 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.
