Statement FROM emp

1. DDL (Data Definition Language) WHERE Sal > ALL (SELECT Sal
a. Create FROM emp
b. Rename WHERE Job In ‘SALESMAN’);
c. Alter ANY
d. Truncate SELECT ename, Sal
e. Drop FROM emp
2. DML (Data Manipulation Language) WHERE Sal > ANY (SELECT Sal
a. Insert FROM emp
b. Update WHERE Job In ‘SALESMAN’);
c. Delete EXIST
3. DCL (Data Control Language) SELECT ename, Sal
a. Grant FROM emp
b. Revoke WHERE Sal > EXIST (SELECT Sal
4. TCL (Transaction Control Language) FROM emp
a. Commit WHERE Job In ‘SALESMAN’);
b. Save Point NOT EXIST
c. Roll Back SELECT ename, Sal
5. DQL (Data Query Language) FROM emp
a. Select WHERE Sal > NOT EXIST (SELECT Sal
b. Projection FROM emp
c. Selection WHERE Job In ‘SALESMAN’);
d. Joins JOINS
GROUP BY CROSS JOIN / NATURAL JOIN
SELECT * / [ Distinct ] col/exp [ [ as] alias name ] SELECT *
FROM table name FROM table 1 , table 2
WHERE <filter-condition> --------- if used WHERE <filter condition>;
GROUP BY col. Name/exp;
HAVING CLAUSE INNER JOIN
SELECT * / [ Distinct ] col/exp [ [ as] alias name ] SELECT *
FROM table name FROM table 1 , table 2
WHERE <filter-condition> --------- if used WHERE <filter condition> and
GROUP BY col. Name/exp; Table 1.comm.col = table 2. Comm..col;
HAVING <Condition on MRF / Condition on Group By
Col/Exp> OUTER JOIN
SELECT *
FROM table 1 , table 2
Outer Query & Inner Query WHERE <filter condition> and
SELECT ename Table 1.comm.col = table 2. Comm..col (+);
FROM emp
WHERE sal < (SELECT sal RIGHT OUTER JOIN
FROM emp SELECT *
WHERE ename IN ‘BLAKE’); FROM table 1 , table 2
Sub Query Operator WHERE <filter condition> and
ALL Table 1.comm.col (+) = table 2. Comm..col;
SELECT ename, Sal
FULL OUTER JOIN
SELECT *
FROM table 1 FULL OUTER JOIN table 2
ON Table 1.comm.col = table 2. Comm..col
WHERE <filter condition> ;

SELF JOIN
SELECT *
FROM table 1 , table 2
WHERE <filter condition> and
Table 1.comm.col = table 2. Comm..col; #1) 100 Series
These are temporary Responses
 100 Continue
INSERT
 101 Switching Protocols
INSERT into table name Values (V1, V2, V3, ………Vn);  102 Processing
#2) 200 Series
UPDATE The client accepts the Request, being processed
UPDATE table name successfully at the server.
SET Col 1 = ‘V1’, Col 2 = ‘V2’, Col n = ‘Vn’  200 – OK
 201 – Created
WHERE <F.C.>;
 202 – Accepted
 203 – Non-Authoritative Information
DELETE  204 – No Content
DELETE  205 – Reset Content
FROM table name  206 – Partial Content
WHERE <F.C.>;  207 – Multi-Status
 208 – Already Reported
 226 – IM Used
CREATE TABLE
#3) 300 Series
CREATE TABLE table_name ( Most of the codes related to this series are for URL
column1 datatype, Redirection.
column2 datatype,  300 – Multiple Choices
column3 datatype,  301 – Moved Permanently
....  302 – Found
 303 – Check Other
 304 – Not Modified
 305 – Use Proxy
 306 – Switch Proxy
 307 – Temporary Redirect
 308 – Permanent Redirect
#4) 400 Series
These are specific to client-side error.
 400 – Bad Request
 401 – Unauthorised
 402 – Payment Required
 403 – Forbidden
 404 – Not Found
 405 – Method Not Allowed
 406 – Not Acceptable
 407 – Proxy Authentication Required
 408 – Request Timeout
);  409 – Conflict
  410 – Gone
 411 – Length Required
 412 – Precondition Failed
 413 – Payload Too Large
 414 – URI Too Long
 415 – Unsupported Media Type
 416 – Range Not Satisfiable
 417 – Expectation Failed
 418 – I’m a teapot
 421 – Misdirected Request
 422 – Unprocessable Entity
 423 – Locked
 424 – Failed Dependency
 426 – Upgrade Required
 428 – Precondition Required
 429 – Too Many Requests Advantages(Pros) of Agile Method:
 431 – Request Header Fields Too Large
 451 – Unavailable For Legal Reasons 1. Frequent Delivery
#5) 500 Series
These are specific to the server-side error. 2. Face-to-Face Communication with clients.
 500 – Internal Server Error
 501 – Not Implemented 3. Efficient design and fulfils the business
 502 – Bad Gateway
requirement.
 503 – Service Unavailable
 504 – Gateway Timeout
4. Anytime changes are acceptable.
 505 – HTTP Version Not Supported
 506 – Variant Also Negotiates 5. It reduces total development time.
 507 – Insufficient Storage
 508 – Loop Detected
 510 – Not Extended Disadvantages(Cons) of Agile Model:
 511 – Network Authentication Required
1. Due to the shortage of formal documents, it
GET: GET request is used to read/retrieve data from a
web server. GET returns an HTTP status code of 200 creates confusion and crucial decisions taken
(OK) if the data is successfully retrieved from the
server. throughout various phases can be
POST: POST request is used to send data (file, form
data, etc.) to the server. On successful creation, it misinterpreted at any time by different team
returns an HTTP status code of 201.
PUT: A PUT request is used to modify the data on the members.
server. It replaces the entire content at a particular
2. Due to the lack of proper documentation, once
location with data that is passed in the body payload.
If there are no resources that match the request, it the project completes and the developers
will generate one.
PATCH: PATCH is similar to PUT request, but the only allotted to another project, maintenance of the
difference is, it modifies a part of the data. It will only
replace the content that you want to update. finished project can become a difficulty.
DELETE: A DELETE request is used to delete the data
on the server at a specified location.