A blog dedicated to Salesforce Ohana

Importance of Equals and Hashcode in Apex

Recently while doing code review, I found that all developers should have fundamental understanding of "Why we should implement always Equals and Hashcode in Apex?"

In this post, I am going to share my knowledge with few examples to understand the importance of Equals and Hashcode in Apex.

Apex provides you an option to define an equal method in your custom types. This Equals method along with Hashcode is must when you are going to use your custom types in Sets and as Map keys. I would recommend to make this approach (Implementation of Equals and Hashcode) as best practice. Equality operator (==) is going to use the Equals operator if it is defined.

Why we need this Equals method?
Let me start with one example to show you the problem if Equals method is not implemented. Below is the custom type I am having -

Now below is the test class to compare two instances of MyCustomType. Both the instances of MyCustomType is having myField value set to 10. So my expectation is that when I will compare both the instances, they should return true. Let's see what will happen. Below is the test class.

But unfortunately, below is what you will get -
You see our test class is failing. Do you know the reason? Let me tell you the reason. The reason for this comparison to fail is that I don't have the Equals method in my MyCustomType implemented. If the Equals method is not implemented, then exact equality operator (===) will be used. As Salesforce's documentation states -

Exact Equality Operator (===)  always checks the exact same memory location. So if X and Y reference the exact the same memory location, then Exact Equality Operator (===) will return true, otherwise false.

But in the above case, I don't have Equals method implemented in my MyCustomType. So it will go for exact equality operator (===), but myCustomType1 and myCustomType2 are not referencing the same memory location. So the expression (myCustomType1 == myCustomType2) returns false.
Solution to the above problem -
Let me implement the Equals method in  and execute the same test method. Let's see what will happen then.

After implementing Equals method, the test will pass. Great.
Now I will explain Equals method in details. If you are coming from Java background, it is little different. So it makes sense to understand the concept well.
Deep Dive into Equals Method -
The method signature is: public Boolean equals(Object o). Very easy right!!!. But as a developer, you need to be aware of something. You can't write equals method like public Boolean equals(MyCustomType o). The reasons are -
  • The above implementation will not overwrite Object implementation and will not work with arguments other than of type MyCustomType 
  • The == operator will not use the equals(MyCustomType o) implementation.
Another point to notice at line# 5 (this === o). Here I have used exact equality operator (===) instead of == operator. The reason is if I have used == operator, then that operator will use the Equals method again. So it will become a recursive call and very soon we will hit by stack overflow.

There is another point to remember. As per the specification, the equals method should return null if null is passed. This is getting checked @ line# 8. But the point to make here is that "null instanceof anything will return false" this is available from API version 32.0 and above.
Before API 32.0, it is not available. So there you need to modify your line#8 like below -
if( ( o == null ) || !(o instanceof MyCustomType))
Great, but why we need this Hashcode then?
Apex documentation states that "If two objects are equal, based on the equals method, hashCode must return the same value".
So you should implement Hashcode also.

There is a good documentation on Salesforce. Here is the link . CLICK HERE.
I recommend everyone to read Effective Java by Joshua Bloch.


No comments:

Post a Comment

Follow Me

Enter your email address:

Delivered by FeedBurner

Popular Posts


Salesforce (95) Apex (42) admin (27) ADM (20) visualforce (20) dev 501 (19) integration (18) learn salesforce (17) 501 (16) SOAP (13) tutorial (11) Certification. (9) Trigger (7) lightning (7) test class (7) unit testing (7) design pattern (6) report (6) trailhead (6) Advanced Admin (5) New Features (5) SOQL (5) css (5) dashboard (5) debug (5) formula (5) javascript (5) mobile (5) salesforce release (5) security (5) service cloud (5) solution management (5) use case (5) JSON (4) Lightning Experience (4) WebSphere (4) best practice (4) cast iron (4) developer (4) github (4) html (4) polymer (4) profiles (4) responsive (4) tdd (4) ui (4) Live Chat (3) Performance (3) Products (3) Sales Cloud (3) Summer15 (3) Tips (3) component (3) deployment (3) dynamic apex (3) event (3) license (3) map (3) mapbox (3) singleton (3) version controlling (3) Advanced Apex (2) Bulkify (2) Distributed Version Controlling (2) Eclipse (2) Force.com IDE (2) Governor Limit (2) IBM (2) Lightning Design System (2) Live Agent (2) Price Book (2) REST (2) SOSL (2) Spring 15 (2) Study Notes. (2) Summer17 (2) ant (2) automation tool (2) basic (2) chatter (2) coding (2) communication (2) console (2) controller (2) documentation (2) flow (2) git (2) jquery (2) logging (2) permission (2) process builder (2) release (2) salesforce1 (2) strategy (2) xml (2) Agent Productivity (1) Asynchronous callout (1) Browser (1) Bulk data load (1) Calendar (1) Canon (1) Case Management (1) Classic (1) Contact Center (1) Continuation (1) Continuous Integration (1) Cookie (1) Custom Metadata (1) Custom Object (1) Decorator Design Pattern (1) Diwali (1) Email (1) Groups (1) Guide (1) Ideas (1) Improvement (1) KPIs (1) LastModifiedDate (1) Metadata (1) Metrics (1) Omni-Channel (1) Opportunity (1) Photo (1) Platform Developer I (1) Product Schedule (1) Profile (1) Public Site (1) Query Plan (1) QuickReference (1) Reports (1) Role (1) Salesforce Optimizer (1) Site (1) Skills (1) Snap-ins (1) Spring 17 (1) Summer14 (1) Summer16 (1) SystemModStamp (1) Users (1) Webservice (1) Winter'15 (1) Winter'17 (1) access (1) agile (1) app (1) approval process (1) aura (1) awesome (1) backup (1) bitbucket (1) book (1) campaign (1) change set (1) code (1) code coverage (1) configuration (1) csv (1) custom button (1) custom settings (1) customization (1) data loader (1) database (1) delegate Admin (1) describe (1) dom (1) dreamforce (1) duplicate (1) dynamic (1) equals (1) error (1) field-level security (1) folder (1) ftp (1) generic (1) gift (1) global describe (1) hashcode (1) import wizard (1) jenkins (1) keynote (1) long running requests (1) monitoring (1) mysql (1) object (1) page layout (1) personal (1) power of one (1) record type (1) relationship (1) request (1) review (1) sub-tab (1) tab (1) username (1) visual workflow (1) workflow (1)

My Trailhead

Total Subscribers

Total Pageviews