Skip to main content

Java script "==" & "===" operator

Java script is an integral part of any web development. To check the equality between two variables or objects it provides us two different ways. One way is "==" which is known as "equality operator" which perform "type coercion" , and other way is using "===" known as "identity operator".
    Let's try to understand their behavior. 
  1. If we're comparing two operands with same data types then both of them will behaves as per our expectation.
    e.g.
    1 == 1 (true) 1===1 (true)
    "one" == "one" (true) "one" === "one" (true)
    3.1 == 3.1 (true) 3.1 === 3.1 (true)
    false == false (true) false === false (true)
    1 == 2 (false) 1 === (false)

  2. Problem comes when we perform equality against two different data source. Means both of the operands are of different data-types. In this scenario equality operator first perform the type coercion, means value of both of them will 1st get converted to same data type.
        e.g. 1st
        "1" == 1, here string "1" will first get converted to number one (1) then comparison will be done resulting into "true".
    
        e.g. 2nd
        "" == 0, here empty string "" will first get converted to number zero (0) then comparison will be done resulting into "true".
                
    So it is preferable to use the parseInt(), & parseFloat() method if we're comparing any string value of number data-type ("1", "3"). Another problem & more confusing point is that type conversing using parseInt() is different from the type conversion used by "type coercion" e.g. empty string "" will get converted to number 0 using type coercion but it will return not a number NaN if we're suing parseInt("") 

    equality operator "=="

    Result

    identity operator "==="

    Result

    null == undefined true null === undefined false
    Infinity == "Infinity" true Infinity === "Infinity" false
    NaN == NaN false NaN === NaN false
    NaN == "NaN" false NaN === "NaN" false
    false == "0" true false === "0" false
    "" == 0 true "" === 0 false
    false == 0 true false === 0 false
    false == "false" false false === "false" false
    true == 1 true true === 1 false
    true == "1" true true === "1" false
    true == "true" false true === "true" false

Comments

Popular posts from this blog

EFCore - Collate function

Search in SQL server query is generally case insensitive (by default or based on database level collation). Suppose we have an employees table with a row having first-name column value as "My-First-Name", so if we want to do the case-sensitive search we have to explicitly use the related collate: In EF 5 (currently in Release Candidate version [RC.2.20475.6]) Collate function got introduced which helps us to use our specific collation based search.  C# with EF5 code sample: var employeeCaseSensitiveSearch = _dbContext.Employees .Where(x => EF.Functions.Collate(x.FirstName, "Latin1_General_CS_AS") == "my-first-name") .FirstOrDefault(); A related database query will be something like this: T-SQL: Case sensitive search (use specific collation e.g.: Latin1_General_CS_AS) SELECT * FROM dbo.Employees AS e WHERE e.FirstName Collate Latin1_General_CS_AS = 'my-first-name' Some of the useful CSharp function which g...

Git - Update submodule

Sometimes in the large project when we separate it in different repositories we need to take reference of one repository in another where some the sub-module concepts. Now if we move our submodule to a different repository or renaming its repo-path then we've to also update the repository where this sub-module is getting referenced. Let's see how to update the git submodule.  Step-1: First clone the repo Step-2: Open git UI to create a new local branch from master  Step-3: Open git bash -- Now run below command to (remove submodules & add them):  -- Remove submodule git submodule deinit YOUR_FIRST_REPO git rm YOUR_FIRST_REPO git commit -m "Removed submodule YOUR_FIRST_REPO" rm -rf .git/modules/YOUR_FIRST_REPO -- Add submodule git submodule add <<..YOUR_FIRST_REPO git URL>> Step-4: All good, let's push our changes to the master

EFCore - Update command is not updating the underlying data

Why my update command using EFCore is not updating the underlying data in the database though in middle-tier code it's successful, not throwing any error? Let's try to get the root cause and how to solve this.  When creating the model class of related database object if the primary key name is Id then no need to explicitly mention the Key in ef-core OnModelCreating.  But if we've key name different from Id then we have to explicitly mention it in our OnModelCreating. Something like this:  entity.HasKey(c => new {c.CustId }); Assume in the database we've Customers table like this: CREATE TABLE [dbo].[Customers]( [CustId] [INT] IDENTITY(1,1) NOT NULL Primary Key, [FirstName] [VARCHAR](50) NULL ) Point to ponder: In the database table, column CustId is already defined as Primary key.  In EFCore model setup, it's up to us to configure the Key as (custId) or configure it as HasNoKey() Assume we've set our entity with Ha...