During the migration activity, most of the time we are facing issues related to Case Sensitivity.
For example,

In Windows Operating System, you cannot create two different directories like: “DBrnd.Com” and “dbrnd.com”. This both consider as same name in Windows Operating System, but In Linux Operating System, You can create both directories separately like: “DBrnd. Com” and “dbrnd.com”.

When we are migrating MySQL Database between two different Operating Systems, we should also take care about the name of Database files and folders.

There are mainly two MySQL Server parameters lower_case_file_system and lower_case_table_names.

A lower_case_file_system parameter ensures about case sensitivity of file names on the file system where the data directory is located.
A lower_case_file_system OFF means file names are Case Sensitive, and ON means file names are Case Insensitive.

A lower_case_table_names parameters ensure about case sensitivity of table names.
If lower_case_table_names = 0, Table name stored as specified, but comparisons are Case Sensitive.
If lower_case_table_names = 1, Table name stored in lower case and comparisons are not Case Sensitive.
If lower_case_table_names = 2, Table name stored as specified, but comparisons are in Lowercase.

In this post, I am sharing a small demonstration on how to perform case-sensitive string comparison in MySQL.

For example, if you are searching string with LIKE ‘a%’, also you get all records of LIKE ‘A%’ – the reason is the case-insensitive comparison.
By default, string comparisons are case insensitive because strings are non-binary. For the case-sensitive comparison, we should use binary collation.

If you need case-sensitive string comparison, you should use this COLLATION latin1_bin.

You can visit this article about, How to change default COLLATION in MySQL.


The String Case Sensitive Comparison using LIKE BINARY:

You can also perform string case-sensitive comparison using LIKE BINARY operator.
Generally, we need for password comparison.

Below is a full demonstration on this:

Create a sample table and data:

CREATE TABLE tbl_Students
(
    StudentID INT AUTO_INCREMENT
    ,StudentName VARCHAR(255)
    ,CONSTRAINT pk_tbl_Students_StudentID PRIMARY KEY (StudentID)
);

INSERT INTO tbl_Students (StudentName) 
VALUES ('Anvesh'),('Roy'),('martin'),('Loris'),('Jenny');

Execute below three queries and check the result:
Using normal LIKE you will get Case insensitive result and using LIKE BINARY you will get the Case sensitive result.

SELECT 
    StudentID
    ,StudentName
FROM tbl_Students WHERE StudentName LIKE 'roy';
-- Return one record of Student 'Roy'

SELECT 
    StudentID
    ,StudentName
FROM tbl_Students WHERE StudentName LIKE BINARY 'roy';
-- No record for Student 'roy' because this is case sensitive check,'roy' and 'Roy' both are different. 

SELECT 
    StudentID
    ,StudentName
FROM tbl_Students WHERE StudentName LIKE BINARY 'Roy';
-- Return one record of Student 'Roy'

Guys, this is one of the important discussion of PostgreSQL.
All identifiers, including column name, are Case-Sensitive in PostgreSQL?

Yes: when you define identifier in the double-quote, it is a Case-Sensitive.
No: when you do not use double-quote for an identifier, it is not a Case-Sensitive.

For example:
With double-quoted:

CREATE TABLE "Test" (rno integer);
SELECT *FROM Test /*True...*/
SELECT *FROM test; /*False...not work*/

Without double-quoted:

CREATE TABLE Test(rno integer);
SELECT *FROM Test /*True...*/
SELECT *FROM teST /*True...*/
SELECT *FROM test /*True...*/

My advice: Never use double-quoted for any identifiers. Otherwise, you will face the problem of case-sensitivity.
When you do not use double-quoted, PostgreSQL internally store all identifiers in small latter and you can access those all identifiers in any case.

When you create your table using PGAdmin UI, by default it creates all identifiers with double-quoted.
Always try to create your database objects by using the SQL script.