On 4 March 2014 14:31, Timothy Lorens <[email protected]> wrote:

> Which means every table needs to have a surrogate ID which to a lot of
> DBA's is bad practice for children/associations.
>

That is a good practice when dealing with ORMs, yes. It is not just an ORM
concept, but really a core concept of what an Entity is.


>
> 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.
>

It doesn't really need to be a DB-level PK as long as you can guarantee
that it is unique.



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.

Reply via email to