SQL CROSS JOIN – Generate All Possible Combinations


Introduction

In SQL, text data types are used to store alphanumeric values like names, addresses, emails, and descriptions. Choosing the correct text type — CHAR, VARCHAR, or TEXT — is important for optimizing storage space, query speed, and database performance.

In this section, you'll learn the definitions, differences, and best use cases for each text data type.




1. CHAR (Fixed-Length String)

CHAR is used to store fixed-length strings. If the stored string is shorter than the defined length, SQL automatically pads it with spaces to match the specified size.



Features:

  • Fixed length
  • Fast and predictable performance
  • Uses extra storage if the data is often shorter than the specified length


Syntax:


column_name CHAR(length);

length = number of characters (1 to 255 depending on the database system)



Example:


CREATE TABLE countries (
country_code CHAR(2),
country_name CHAR(50)
    );

country_code like 'US', 'IN', 'UK' will always take 2 characters.



When to Use CHAR:


  • Data with a constant size, such as country codes, gender ('M', 'F'), state abbreviations
  • Fixed-format fields like credit card types ('VISA', 'MC')
  • When exact storage size is known and consistent



2. VARCHAR (Variable-Length String)

VARCHAR stands for Variable Character. It stores variable-length strings, meaning only the actual characters are stored without unnecessary padding.



Features:


  • Variable length
  • More space-efficient than CHAR for varying-length text
  • Slightly slower than CHAR when processing large volumes (because of extra calculations for string lengths)


Syntax:


column_name VARCHAR(length);

length = maximum number of characters allowed



Example:


CREATE TABLE employees (
first_name VARCHAR(50),
email VARCHAR(100)
    );

Names and emails can vary in length, making VARCHAR ideal.



When to Use VARCHAR:


  • Data with unpredictable or variable length
  • Names, emails, addresses, and descriptions under 255-65535 characters
  • Most general-purpose text fields




3. TEXT (Large Text Field)

TEXT is used to store large amounts of text like long descriptions, blog posts, comments, or articles.



Features:

  • Meant for large text storage (up to 65,535 characters for standard TEXT in MySQL)
  • Cannot have a default value (in some databases like MySQL)
  • TEXT fields are stored outside the main table with a pointer reference
  • Different variants exist (TINYTEXT, MEDIUMTEXT, LONGTEXT) for various sizes


Syntax:


column_name TEXT;


Example:


CREATE TABLE articles (
id INT,
title VARCHAR(255),
body TEXT
   );

body will store the full article content, which can be very large.



When to Use TEXT:


  • Long-form text fields (comments, articles, reviews, reports)
  • Data that exceeds normal VARCHAR limits
  • When exact storage requirements are unknown or potentially very large



Quick Comparison: CHAR vs VARCHAR vs TEXT


Feature CHAR VARCHAR TEXT
Storage Fixed length Variable length Variable, large storage
Max Size Up to 255 chars 65,535 bytes (typically) 65,535+ chars (depends on type)
Performance Fast for fixed-size Efficient for variable text Slightly slower for queries
Indexing Full index support Full index support Limited in some DBs
Best Use Case Codes, fixed formats Names, addresses, emails Articles, long descriptions



Important Tips


  • Use CHAR only when all values will be exactly the same length
  • VARCHAR is the best choice for most standard text fields
  • Reserve TEXT for content that exceeds VARCHAR limits
  • Consider VARCHAR(MAX) in SQL Server for large text that might need indexing
  • Be aware that TEXT fields may have limitations on default values and full-text indexing


What is a CROSS JOIN in SQL?

A CROSS JOIN returns the Cartesian product of two tables. This means it pairs every row from the first table with every row from the second table — even if there's no logical relationship between them.

It's useful for generating combinations of items, such as:

  • All possible pairings of products and sizes
  • Scheduling scenarios
  • Matrix-style data

CROSS JOIN Syntax

SELECT *
FROM table1
CROSS JOIN table2;

There is no ON clause because it does not require a join condition.

Real-Life Example

Table: products

idproduct_name
1T-Shirt
2Hoodie

Table: sizes

idsize
1Small
2Medium
3Large

CROSS JOIN Query

SELECT 
  products.product_name, 
  sizes.size
FROM products
CROSS JOIN sizes;

Result:

product_namesize
T-ShirtSmall
T-ShirtMedium
T-ShirtLarge
HoodieSmall
HoodieMedium
HoodieLarge

You get all possible combinations of products and sizes.

Use Cases for CROSS JOIN

  • Generating test data or combinations
  • Creating price matrix tables
  • Matching every row with every other row
  • Calculating combinations or permutations

CROSS JOIN vs Other Joins

JOIN Type Purpose Requires Join Condition
INNER JOIN Matching rows in both tables Yes
LEFT JOIN All left rows + matching right Yes
RIGHT JOIN All right rows + matching left Yes
FULL OUTER JOIN All rows from both tables Yes
CROSS JOIN All combinations (Cartesian product) No

Caution

A CROSS JOIN can produce very large results quickly. If you join a table with 100 rows and another with 1000 rows, you'll get 100,000 rows in the result. Use carefully.

Conclusion

A CROSS JOIN is a powerful SQL operation for producing all possible row combinations from two tables. Though rarely used in everyday queries, it's valuable for data generation, reporting models, and combination logic.