MySQL_DAY_1
MySQL_DAY_1
tables
• Can create
relationship
• DDL – Data
Definition Language
• DML – Data
Manipulation
Language
• TCL – Transaction
Control Language
• DQL – Data Query
Language
• DCL – Data Control
Language
CREATE:-
CREATE [TABLE | VIEW | INDEX | USER | ... ]
[name] (
[column1_name] [data_type] [constraint1] [constraint2],
[column2_name] [data_type] [constraint1] [constraint2],
...
DATA )
UPDATE:-
DATA UPDATE [table_name]
MANIPULATIO SET [column1] = [new_value1], [column2] =
N LANGUAGE [new_value2], ...
WHERE [condition];
DELETE:-
DELETE FROM [table_name]
WHERE [condition];
SELECT:-
SELECT [column1], [column2], ...
FROM [table_name]
DATA QUERY WHERE [condition]
LANGUAGE [ORDER BY [column] [ASC/DESC]]
[LIMIT [number]];
1. COMMIT:
Syntax: COMMIT;
Function: Permanently saves changes made within a transaction
to the database.
2. ROLLBACK:
TRANSACTIO Syntax: ROLLBACK;
LANGUAGE TO [grantee_list]
FROM [grantee_list]
[CASCADE | RESTRICT];
These are constraints applied within a single table,
ensuring individual data values are valid and complete.
Common types include:
• Primary Key (PK): A unique identifier for each row
in a table, ensuring no duplicates.
ENTITY • Unique: Prevents duplicate values in a specific
column.
CONSTRAIN • NOT NULL: Disallows null values in a column.
TS • CHECK: Defines a logical expression for valid values
in a column.
• DEFAULT: Specifies a value automatically inserted
when a column is left blank.
• Primary Key (PK): • CHECK:
CREATE TABLE [table_name] ( CREATE TABLE [table_name] (
[column_name1] [data_type] PRIMARY KEY, [column_name1] [data_type] CHECK
([validation_expression]),
...
); ...
• Unique: );
CREATE TABLE [table_name] (
[column_name1] [data_type] UNIQUE, • DEFAULT:
...
CREATE TABLE [table_name] (
);
[column_name1] [data_type] DEFAULT [default_value],
• NOT NULL: ...
CREATE TABLE [table_name] ( );
[column_name1] [data_type] NOT NULL,
...
);
These connect two tables, ensuring data relationships
REFERENTIA are valid. The main type is:
• Foreign Key (FK): References a primary key in
L another table, guaranteeing data consistency
CONSTRAINT between tables. This prevents orphaned records (data
in one table without a corresponding record in the
S other).
•Foreign Key (FK):
ALTER TABLE [child_table_name]
ADD CONSTRAINT [constraint_name]
FOREIGN KEY ([child_column_name])
REFERENCES [parent_table_name] ([parent_column_name])
[ON DELETE [action]]
[ON UPDATE [action]];
2. Trigger Functions:-
CREATE TRIGGER price_check
BEFORE INSERT ON products
FOR EACH ROW
SET NEW.price = NULL
WHERE NEW.price < NEW.cost;
Implicit, across
Scope Single table Multiple tables
database