Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I have some repository methods which can update an whole entity or its parts (for example, when a user approves an invitation all i need to update is only “Approved” field).
What is the best practice for passing parameters in such repo methods? Should i pass a whole entity “Invitation” and use only one field for updation or should i pass only entity’s ID and the “Approved” value? Thanks.
I recommend passing the entity itself if you already have it. If you’ve already queried for it why make the repository query again?
The only time I pass an id around is in situations I don’t already have the object, but that’s pretty rare, as once I get the ID in the controller I tend to query for the object right there.