FIX:Updated Operators and datatypes of SQL

[DIYA-bot]

Description

Fixes # (issue)

Type of Change

• New feature (e.g., new page, component, or functionality)
• Bug fix (non-breaking change that fixes an issue)
• UI/UX improvement (design, layout, or styling updates)
• Performance optimization (e.g., code splitting, caching)
• Documentation update (README, contribution guidelines, etc.)
• Other (please specify):

Changes Made

Dependencies

• List any new dependencies or tools required for this change.
• Mention any version updates or configurations that need to be considered.

Checklist

• My code follows the style guidelines of this project.
• I have tested my changes across major browsers and devices
• My changes do not generate new console warnings or errors .
• I ran npm run build and attached screenshot(s) in this PR.
• This is already assigned Issue to me, not an unassigned issue.

[vercel]

@DIYA-bot is attempting to deploy a commit to the recode Team on Vercel.

A member of the Team first needs to authorize it.

[github-actions]

Thank you for submitting your pull request! 🙌 We'll review it as soon as possible. The estimated time for response is 5–8 hrs.

In the meantime, please provide all necessary screenshots and make sure you run - npm build run , command and provide a screenshot, a video recording, or an image of the update you made below, which helps speed up the review and assignment. If you have questions, reach out to LinkedIn. Your contributions are highly appreciated!😊

Note: I maintain the repo issue every day twice at 8:00 AM IST and 9:00 PM IST. If your PR goes stale for more than one day, you can tag and comment on this same issue by tagging @sanjay-kv.

We are here to help you on this journey of open source. Consistent 20 contributions are eligible for sponsorship 💰

🎁 check our list of amazing people we sponsored so far: GitHub Sponsorship. ✨

📚Your perks for contribution to this community 👇🏻

1. Get free Consultation use code recode50 to get free: Mentorship for free.

2. Get the Ebook for free use code recode at checkout: Data Science cheatsheet for Beginners.

3. Check out this weekly Newsletter: Sanjay's Newsletter.

If there are any specific instructions or feedback regarding your PR, we'll provide them here. Thanks again for your contribution! 😊

[vercel]

Front matter should begin immediately without blank lines - lines 1-3 contain unnecessary blank lines before the --- separator.

View Details

📝 Patch Details

diff --git a/docs/sql/SQL-basics/datatypes.md b/docs/sql/SQL-basics/datatypes.md
index d371913..c44a2f1 100644
--- a/docs/sql/SQL-basics/datatypes.md
+++ b/docs/sql/SQL-basics/datatypes.md
@@ -1,6 +1,3 @@
-
-
-
 ---
 id: sql-datatypes
 title: SQL Data Types
@@ -35,11 +32,11 @@ Data types are super important because they:
 
 Imagine a `students` table. Data types ensure the `student_id` is a number, `first_name` is text, and `enrollment_date` is a date.
 
-Here’s a handy overview to get you started:
+Here's a handy overview to get you started:
 
 
 :::tip Pro Tip
-Always pick the smallest, most appropriate data type for your data. For example, don’t use a text type for numbers you want to do math on!
+Always pick the smallest, most appropriate data type for your data. For example, don't use a text type for numbers you want to do math on!
 :::
 
 ---
@@ -112,7 +109,7 @@ In our students table, we used INT UNSIGNED for student_id. This is perfect beca
 Use UNSIGNED for any number column that can never be negative (like an ID, age, or stock quantity).
 :::
 ✅ What You've Learned
-Great job! You’ve explored the most important SQL data types:
+Great job! You've explored the most important SQL data types:
 Numeric Types: INT, DECIMAL (for precision), and FLOAT.
 String Types: CHAR (fixed) vs. VARCHAR (variable).
 Date/Time Types: DATE, DATETIME, and TIMESTAMP.

Analysis

YAML front matter parsing fails due to blank lines before --- separator

What fails: Docusaurus YAML front matter parser doesn't recognize front matter when preceded by blank lines in docs/sql/SQL-basics/datatypes.md

How to reproduce:

# Test front matter parsing with regex used by Docusaurus
node -e "
const fs = require('fs');
const content = fs.readFileSync('docs/sql/SQL-basics/datatypes.md', 'utf8');
const regex = /^---\n([\s\S]*?)\n---/;
const match = content.match(regex);
console.log('Front matter detected:', !!match);
"

Result: Returns Front matter detected: false when file starts with blank lines before ---

Expected: Should return Front matter detected: true for proper YAML parsing per Docusaurus markdown documentation and YAML front matter standards which require front matter to begin on the first line

[vercel]

Suggested change

	GitHub,git,version control
	Introduction of GitHub,
	What is GitHub,
	Why learn GitHub,
	What is GitHub, open source
	Why learn GitHub,beginner guide
	How to use GitHub,
	]
	description: In this tutorial, you will learn about GitHub, its importance, what is GitHub from Scratch, how to use GitHub, steps to start using GitHub, and more.
	---
	description: New to GitHub? This beginner's guide explains what Git and GitHub are, why they're essential for developers, and how to start your open-source journey. Learn key concepts like repositories, commits, and pull requests.
	GitHub,git,version control,
	Introduction of GitHub,
	What is GitHub, open source,
	Why learn GitHub,beginner guide,
	How to use GitHub,
	]
	description: New to GitHub? This beginner's guide explains what Git and GitHub are, why they're essential for developers, and how to start your open-source journey. Learn key concepts like repositories, commits, and pull requests.
	---

Missing commas in YAML array causes invalid syntax, and front matter is missing its closing --- separator.

View Details

Analysis

YAML front matter parsing errors in intro-github.md

What fails: YAML front matter in docs/Technical/intro-github.md has invalid flow sequence syntax and missing closing separator, causing incorrect tag parsing and front matter extraction failure

How to reproduce:

# Test YAML parsing with js-yaml
node -e "const yaml=require('js-yaml'); console.log(yaml.load(frontMatter).tags)"
# Results in concatenated tags: ["GitHub", "git", "version control Introduction of GitHub"]

# Test front matter extraction  
node -e "console.log('---\\ndata\\n---\\ncontent'.match(/^---\\s*\\n([\\s\\S]*?)\\n---/))"
# Returns null due to missing closing ---

Result: Tags array incorrectly parses as 6 items instead of 9, with values concatenated (e.g., "version control Introduction of GitHub"). Front matter extraction fails completely without closing --- separator.

Expected: Tags should parse as 9 separate items. Front matter should be properly delimited per YAML specification requiring commas in flow sequences and Jekyll front matter requiring closing ---.

[vercel]

The frontmatter is malformed - the opening --- delimiter is missing. The file starts with title: on line 1 instead of ---.

View Details

📝 Patch Details

diff --git a/blog/spark-architecture/index.md b/blog/spark-architecture/index.md
index e4b0784..5d698a1 100644
--- a/blog/spark-architecture/index.md
+++ b/blog/spark-architecture/index.md
@@ -1,3 +1,4 @@
+---
 title: "Spark Architecture Explained"
 authors: [Aditya-Singh-Rathore,sanjay-kv]
 sidebar_label: "Spark Architecture Explained"

Analysis

Missing frontmatter opening delimiter in blog/spark-architecture/index.md breaks metadata parsing

What fails: File blog/spark-architecture/index.md frontmatter missing opening --- delimiter prevents Docusaurus from parsing blog metadata (title, authors, tags, date, description)

How to reproduce:

# Test frontmatter parsing with gray-matter (Docusaurus's parser):
node -e "
const matter = require('gray-matter');
const fs = require('fs');
const content = fs.readFileSync('blog/spark-architecture/index.md', 'utf8');
console.log('Metadata parsed:', Object.keys(matter(content).data).length > 0);
"

Result: Returns false - no metadata fields recognized. File starts with title: instead of proper ---\ntitle: format

Expected: Should return true with 7 metadata fields (title, authors, tags, etc.) parsed per Docusaurus frontmatter specification

[vercel]

The file has invalid frontmatter syntax with a malformed - --- marker on line 3 that breaks the YAML frontmatter block.

View Details

📝 Patch Details

diff --git a/docs/sql/SQL-basics/Operators.md b/docs/sql/SQL-basics/Operators.md
index 50fd12f..a886f9b 100644
--- a/docs/sql/SQL-basics/Operators.md
+++ b/docs/sql/SQL-basics/Operators.md
@@ -1,6 +1,4 @@
-
-
-- ---
+---
 id: sql-operators
 title: SQL Operators
 sidebar_label: SQL Operators
@@ -66,4 +64,4 @@ INSERT INTO products VALUES (1, 15.99, 10), (2, 25.50, 5);
 SELECT id, price, quantity, 
        price * quantity AS total_value,
        price + 2.00 AS price_with_tax
-FROM products;
+FROM products;
\ No newline at end of file

Analysis

Invalid YAML frontmatter syntax breaks Docusaurus parsing

What fails: docs/sql/SQL-basics/Operators.md has malformed frontmatter with - --- delimiter instead of ---, causing markdown parser to fail

How to reproduce:

npm run build
# Would cause frontmatter parsing error for Operators.md

Result: The frontmatter block starting with - --- is invalid YAML syntax that prevents proper metadata extraction

Expected: Frontmatter must start with --- on the first line per Docusaurus documentation - "Front matter is provided at the very top of the file, enclosed by three dashes ---"

[vercel]

Suggested change

	Now, let's break down the types we used.
	```
	Now, let's break down the types we used.

Missing blank line between code block and text causes formatting to run together, and line 70 has run-on text that should be separated.

View Details

Analysis

Unclosed SQL code block breaks markdown formatting in datatypes.md

What fails: SQL code block starting at line 54 with ```sql never gets closed, causing all subsequent content to render as code instead of formatted markdown

How to reproduce:

# View the file in any markdown renderer
cat docs/sql/SQL-basics/datatypes.md | grep -A 20 "SELECT \* FROM students;"

Result: Text "Now, let's break down the types we used." and heading "## Numeric Data Types (Numbers)" render as plain code text instead of formatted markdown

Expected: Code block should be properly closed with ``` followed by blank lines, allowing subsequent text and headings to render correctly per CommonMark spec requirements for fenced code blocks

[sheikhlimon]

Thanks for your PR! For future contributions, it’s best to create a separate branch instead of working directly on main. This helps keep things organized and makes reviews easier.

[sheikhlimon]

@DIYA-bot check the contributing guidelines

[sanjay-kv]

@DIYA-bot closing this as i havnt assigned any related issues and the docs change is across 10 blogs instead of sql

[DIYA-bot]

Ok> @DIYA-bot check the contributing guidelines