No I disagree. The application should be able to provide this
assistance for me. I shouldn't have to make these checks in every
instance every time. That puts a lot of responsibility on the
developer and creates overhead. The whole point of a framework is to
provide that assistance so the
http://www.symfony-project.org/plugins/tbDuplicateKeyPlugin
On Apr 1, 1:09 pm, Joshua houseaddi...@gmail.com wrote:
No I disagree. The application should be able to provide this
assistance for me. I shouldn't have to make these checks in every
instance every time. That puts a lot of
I would suggest this comes down to application design and logic.
Your business logic should not be creating duplicates of SomeClass if
the instance already exists.
You can do one of two things:
1) Do a lookup to see if the key already exists
2) Add a try catch block around the statement and
