html-flip-book-react 0.0.0-alpha.1

package/example/assets/pages_data/en/content/018-essential-mysql-functions.md

@@ -0,0 +1,190 @@
+# Essential MySQL Functions
+
+MySQL has many built-in functions. We will covering some important most used built-in functions; for a complete list refer to the online MySQL Reference Manual (http://dev.mysql.com/doc/).
+
+> NOTE: As of now we will be going through only function and their output, as they would be self explanatory.
+
+## Numeric Functions
+```sql
+SELECT ROUND(5.73)
+   ```
+6
+
+```sql
+SELECT ROUND(5.73, 1)
+   ```
+5.7
+
+```sql
+SELECT TRUNCATE(5.7582, 2)
+   ```
+5.75
+
+```sql
+SELECT CEILING(5.2)
+   ```
+6
+
+```sql
+SELECT FLOOR(5.7)
+   ```
+5
+
+```sql
+SELECT ABS(-5.2)
+   ```
+5.2
+
+```sql
+SELECT RAND() -- Generates a random floating point number b/w 0 & 1
+   ```
+
+## STRING Functions
+```sql
+SELECT LENGTH('sky')
+   ```
+3
+
+```sql
+SELECT UPPER('sky')
+   ```
+SKY
+
+```sql
+SELECT LOWER('sky)
+   ```
+sky
+
+```sql
+SELECT LTRIM('    sky')
+   ```
+sky
+
+```sql
+SELECT RTRIM('sky    ')
+   ```
+sky
+
+```sql
+SELECT TRIM('   sky  ')
+   ```
+sky
+
+```sql
+SELECT LEFT('Kindergarten', 4)
+   ```
+Kind
+
+```sql
+SELECT RIGHT('Kindergarten', 6)
+   ```
+garten
+
+```sql
+SELECT SUBSTRING('Kindergarten', 3, 5)
+   ```
+nderg
+
+```sql
+SELECT LOCATE('n','Kindergarten') -- LOCATE returns the first occurrence of a character or character string, if found, otherwise it returns 0
+   ```
+3
+
+```sql
+SELECT REPLACE('Kindergarten', 'garten', 'garden')
+   ```
+Kindergarden
+
+```sql
+SELECT CONCAT('first', 'last')
+   ```
+firstlast
+
+## DATE Functions
+```sql
+SELECT NOW()
+   ```
+2021-10-21 19:59:47
+
+```sql
+SELECT CURDATE()
+   ```
+2021-10-21
+
+```sql
+SELECT CURTIME()
+   ```
+20:01:12
+
+```sql
+SELECT MONTH(NOW())
+   ```
+10
+
+```sql
+SELECT YEAR(NOW())
+   ```
+2021
+
+```sql
+SELECT HOUR(NOW())
+   ```
+13
+
+```sql
+SELECT DAYTIME(NOW())
+   ```
+Thursday
+
+## Formatting Dates and Times
+
+> In MySQL, the default date format is "YYYY-MM-DD", ex: "2025-05-12", MySQL allows developers to format it the way they want. We will discuss some of them.
+```sql
+SELECT DATE_FORMAT(NOW(), '%M %D %Y')
+   ```
+October 22nd 2021
+
+```sql
+SELECT DATE_FORMAT(NOW(), '%m %d %y')
+   ```
+10 22 21
+
+```sql
+SELECT DATE_FORMAT(NOW(), '%m %D %y')
+   ```
+10 22nd 21
+
+```sql
+SELECT TIME_FORMAT(NOW(), '%H %i %p')
+   ```
+14:11 PM
+
+## Calculating Dates and Times
+
+```sql
+SELECT DATE_ADD(NOW(), INTERVAL 1 DAY) --return tomorrows date and time
+   ```
+
+2021-10-23 14:26:17
+
+```sql
+SELECT DATE_ADD(NOW(), INTERVAL -1 YEAR)
+   ```
+or
+```sql
+SELECT DATE_SUB(NOW(), INTERVAL 1 YEAR)
+   ```
+> Both the queries will return the same output
+
+2020-10-22 14:29:47
+
+```sql
+SELECT DATEDIFF('2021-09-08 09:00', '2021-07-07 17:00') -- It will return the difference in number of days, time won't be considered
+   ```
+
+63
+
+```sql
+SELECT TIME_TO_SEC('09:00') - TIME_TO_SEC('09:02')
+   ```
+-120

package/example/assets/pages_data/en/content/019-triggers-in-sql.md

@@ -0,0 +1,133 @@
+# Triggers In SQL
+
+A `trigger` is a stored procedure in database which is automatically invoked whenever any special event occurs in the database. The event can be any event including INSERT, UPDATE and DELETE.
+
+For eg: If you want  to perfom a task after a record is inserted into the table then we can make use of `triggers`
+
+#### Syntax for creating triggers
+
+```
+create trigger [trigger_name]
+[before | after]
+{insert | update | delete}
+on [table_name]
+[for each row | for each column]
+[trigger_body]
+```
+
+`create trigger [trigger_name]` : Creates or replaces an existing trigger with the trigger_name.
+
+`[before | after]` : Now we can specify when our trigger will get fired. It can be before  updating the database or after updating the database.
+
+Generally , `before` triggers are used to validate the data before storing it into the database.
+
+`{insert | update | delete} `: Now, we  specify the `DML operation` for which our trigger should get fired .
+
+`on [table_name]` : Here, we specify the name of the table which is associated with the trigger.
+
+`[for each row]` : This specifies a row-level trigger, i.e., the trigger will be executed for each row being affected.
+
+`[for each column]` : This specifies a column-level trigger, i.e., the trigger will be executed after the specified column is affected.
+
+`[trigger_body`] : Here, we specify the operations to be performed once the trigger is fired.
+
+### Show Trigger
+
+If you want to see all the triggers that are present in your database.
+
+```
+show triggers in database_name;
+```
+
+### Drop Trigger
+
+if you no longer want your trigger then you may delete it.
+
+```
+drop trigger trigger_name;
+```
+
+# Example :
+
+Let us consider we have our database named `library`. Consider a scenario where we want a trigger which is fired everytime any particular book is inserted into the `books` table . The `trigger` should add the logs of all the books that are inserted into the `books` table.
+
+We have created two tables :
+
+1. `books` :  It will store all the books available in the library
+2. bookrecord : It will generate a statement a log for the inserted book
+
+```
+Select * from library.books;
+```
+
+```
++----------+---------------+
+| book_id  | book_name     |
++----------+---------------+
+| 	   | 		   |
+| 	   | 		   |
++----------+---------------+
+```
+
+Here, `book_id` is an auto-incremental field.
+
+```
+Select * from library.bookrecord;
+```
+
+```
++----------+---------------+-----------+
+| SRNO     | bookid        | statement |
++----------+---------------+-----------+
+|          |               |           |
+|          | 		   |           |
++----------+---------------+-----------+
+```
+
+Here, `SRNO` is an auto-incremental field.
+
+Now, we will create our trigger on the `books` table
+
+```
+create trigger library.addstatement
+after insert
+on library.books
+for each row
+insert into library.bookrecord(bookid,statement) values (NEW.book_id,concat('New book named ',NEW.book_name,"  added at ",curdate()));
+```
+
+In MySQL, `NEW` is used to access the currently inserted row. We are inserting the log for the currently inserted book in our database.
+
+Now we will insert a book and wait for the output.
+
+```
+insert into library.books(book_name) values ("Harry Potter and the Goblet of fire");
+```
+
+Output for `books`:
+
+```
++----------+-----------------------------------------------+
+| book_id  | book_name  				   |
++----------+-----------------------------------------------+
+|    1	   | 	Harry Potter and the Goblet of fire	   |
+| 	   | 		  				   |
++----------+-----------------------------------------------+
+```
+
+Output for `bookrecord`:
+
+```
++----------+---------------+----------------------------------------------------------------------------------+
+| SRNO     | bookid        | statement									      |
++----------+---------------+----------------------------------------------------------------------------------+
+|   1      |      1        |     New book named Harry Potter and the Goblet of fire  added at 2021-10-22      |
+|          | 		   |          									      |
++----------+---------------+----------------------------------------------------------------------------------+
+```
+
+See. it worked!!
+
+#### Conclusion:
+
+Here, you learnt what are triggers and how you create them. You can create different types of triggers based on your needs and requirements.

package/example/assets/pages_data/en/content/020-TCL-commands.md

@@ -0,0 +1,154 @@
+# `Transaction Control Language`
+
+  - `Transaction Control Language` can be defined as the portion of a database language used for `maintaining consistency` of the database and `managing transactions` in the database.
+
+  - A set of `SQL statements` that are `co-related logically and executed on the data stored in the table` is known as a `transaction`.
+
+## `TCL` Commands
+
+- `COMMIT` Command
+- `ROLLBACK` Command
+- `SAVEPOINT` Command
+
+## `COMMIT`
+
+The main use of `COMMIT` command is to `make the transaction permanent`. If there is a need for any transaction to be done in the database that transaction permanent through commit command.
+
+### Syntax
+```sql
+COMMIT;
+```
+
+## `ROLLBACK`
+
+Using this command, the database can be `restored to the last committed state`. Additionally, it is also used with savepoint command for jumping to a savepoint in a transaction.
+
+### Syntax
+```sql
+ROLLBACK TO savepoint-name;
+```
+
+## `SAVEPOINT`
+
+The main use of the Savepoint command is to save a transaction temporarily. This way users can rollback to the point whenever it is needed.
+
+### Syntax
+```sql
+SAVEPOINT savepoint-name;
+```
+
+## Examples
+
+#### This is purchase table that we are going to use through this tutorial
+
+| item         | price | customer_name |
+|--------------|-------|---------------|
+| Pen          |    10 | Sanskriti     |
+| Bag          |  1000 | Sanskriti     |
+| Vegetables   |   500 | Sanskriti     |
+| Shoes        |  5000 | Sanskriti     |
+| Water Bottle |   800 | XYZ           |
+| Mouse        |   120 | ABC           |
+| Sun Glasses  |  1350 | ABC           |
+
+```sql
+UPDATE purchase SET price = 20 WHERE item = "Pen";
+```
+##### O/P :  Query OK, 1 row affected (3.02 sec) (Update the price of Pen set it from 10 to 20)
+
+```sql
+SELECT * FROM purchase;
+```
+##### O/P
+| item         | price | customer_name |
+|--------------|-------|---------------|
+| Pen          |    20 | Sanskriti     |
+| Bag          |  1000 | Sanskriti     |
+| Vegetables   |   500 | Sanskriti     |
+| Shoes        |  5000 | Sanskriti     |
+| Water Bottle |   800 | XYZ           |
+| Mouse        |   120 | ABC           |
+| Sun Glasses  |  1350 | ABC           |
+
+```sql
+START TRANSACTION;
+```
+##### Start transaction
+
+```sql
+COMMIT;
+```
+##### Saved/ Confirmed the transactions till this point
+
+```sql
+ROLLBACK;
+```
+##### Lets consider we tried to rollback above transaction
+
+```sql
+SELECT * FROM purchase;
+```
+#### O/P:
+| item         | price | customer_name |
+|--------------|-------|---------------|
+| Pen          |    20 | Sanskriti     |
+| Bag          |  1000 | Sanskriti     |
+| Vegetables   |   500 | Sanskriti     |
+| Shoes        |  5000 | Sanskriti     |
+| Water Bottle |   800 | XYZ           |
+| Mouse        |   120 | ABC           |
+| Sun Glasses  |  1350 | ABC           |
+##### As we have committed the transactions the `rollback` will not affect anything
+
+```sql
+SAVEPOINT  sv_update;
+```
+##### Create the `savepoint` the transactions above this will not be rollbacked
+
+```sql
+UPDATE purchase SET price = 30 WHERE item = "Pen";
+```
+#### O/P : Query OK, 1 row affected (0.57 sec)
+#### Rows matched: 1  Changed: 1  Warnings: 0
+
+```sql
+SELECT * FROM purchase;
+```
+
+| item         | price | customer_name |
+|--------------|-------|---------------|
+| Pen          |    30 | Sanskriti     |
+| Bag          |  1000 | Sanskriti     |
+| Vegetables   |   500 | Sanskriti     |
+| Shoes        |  5000 | Sanskriti     |
+| Water Bottle |   800 | XYZ           |
+| Mouse        |   120 | ABC           |
+| Sun Glasses  |  1350 | ABC           |
+##### price of pen is changed to 30 using the `update` command
+
+```sql
+ROLLBACK to sv_update;
+```
+##### Now if we `rollback` to the `savepoint` price should be 20 after `rollback` lets see
+
+```sql
+SELECT * FROM purchase;
+```
+
+| item         | price | customer_name |
+|--------------|-------|---------------|
+| Pen          |    20 | Sanskriti     |
+| Bag          |  1000 | Sanskriti     |
+| Vegetables   |   500 | Sanskriti     |
+| Shoes        |  5000 | Sanskriti     |
+| Water Bottle |   800 | XYZ           |
+| Mouse        |   120 | ABC           |
+| Sun Glasses  |  1350 | ABC           |
+| Torch        |   850 | ABC           |
+##### As expected we can see `update` query is rollbacked to sv_update.
+
+
+
+## Conclusion
+
+With this short tutorial we have learnt TCL commands.

package/example/assets/pages_data/en/content/021-DCL-commands.md

@@ -0,0 +1,126 @@
+# `Data Control Language`
+DCL commands are used to grant and take back authority from any database user.
+
+## `DCL` Commands
+- `GRANT` Command
+- `REVOKE` Command
+
+## `GRANT`
+`GRANT` is used to give user access privileges to a database.
+
+### Syntax
+```sql
+GRANT privilege_name ON objectname TO user;
+```
+
+## `REVOKE`
+`REVOKE` remove a privilege from a user. REVOKE helps the owner to cancel previously granted permissions.
+
+
+### Syntax
+```sql
+REVOKE privilege_name ON objectname FROM user;
+```
+
+### `DCL` Examples
+```sql
+SELECT * FROM purchase;
+```
+Output:
+```
+| item         | price | customer_name |
+|--------------|-------|---------------|
+| Pen          |    20 | Sanskriti     |
+| Bag          |  1000 | Sanskriti     |
+| Vegetables   |   500 | Sanskriti     |
+| Shoes        |  5000 | Sanskriti     |
+| Water Bottle |   800 | XYZ           |
+| Mouse        |   120 | ABC           |
+| Sun Glasses  |  1350 | ABC           |
+| Torch        |   850 | ABC           |
+```
+
+- Lets start with `GRANT` command:
+
+```sql
+  GRANT INSERT ON purchase TO 'Sanskriti'@'localhost';
+```
+Output:
+```
+#### O/P Query OK, 0 rows affected (0.31 sec)
+```
+
+Description In above command we have granted user Sanskriti priviledge to `Insert` into purchase table.
+
+- Now if I login as Sanskriti and try to run `Select` statement as given below what should happen?
+
+```sql
+SELECT * FROM purchase;
+```
+
+Output:
+```
+#### O/P ERROR 1142 (42000): SELECT command denied to user 'Sanskriti'@'localhost' for table 'purchase'
+```
+Yup as expected it gives error because we have granted insert operation to Sanskriti.
+
+- So lets try inserting data to purchase table:
+```sql
+INSERT INTO purchase values("Laptop", 100000, "Sanskriti");
+```
+
+Output:
+```
+#### O/P Query OK, 1 row affected (0.34 sec)
+```
+Yes! It works!
+
+- Now I am checking the purchase table from my original account:
+```sql
+SELECT * FROM purchase;
+```
+
+Output:
+```
+| item         | price  | customer_name |
+|-------------|--------|---------------|
+| Pen          |     20 | Sanskriti     |
+| Bag          |   1000 | Sanskriti     |
+| Vegetables   |    500 | Sanskriti     |
+| Shoes        |   5000 | Sanskriti     |
+| Water Bottle |    800 | XYZ           |
+| Mouse        |    120 | ABC           |
+| Sun Glasses  |   1350 | ABC           |
+| Torch        |    850 | ABC           |
+| Laptop       | 100000 | Sanskriti     |
+```
+
+As you can see, the row is inserted.
+
+- Now lets try `Revoke` command:
+
+```sql
+REVOKE INSERT ON purchase FROM 'Sanskriti'@'localhost';
+```
+
+Output:
+```
+#### O/P Query OK, 0 rows affected (0.35 sec)
+```
+
+Now we have revoked the insert priviledge from Sanskriti.
+
+- If Sanskriti runs insert statement it should give error:
+
+```sql
+INSERT INTO purchase values("Laptop", 100000, "Sanskriti");
+```
+
+Output:
+```
+#### O/P ERROR 1142 (42000): INSERT command denied to user 'Sanskriti'@'localhost' for table 'purchase'
+```
+
+## Conclusion
+
+Through this tutorial we have learnt `DCL` commands and their usage.

package/example/assets/pages_data/en/content/100-mysqldump.md

@@ -0,0 +1,109 @@
+# The MySQL dump command
+
+There are many ways and tools on how to export or backup your MySQL databases. In my opinion, `mysqldump` is a great tool to accomplish this task.
+
+The mysqldump tool can be used to dump a database or a collection of databases for backup or transfer to another database server (not necessarily MariaDB or MySQL). The dump typically contains SQL statements to create the table, populate it, or both.
+
+One of the main benefits of mysqldump is that it is available out of the box on almost all shared hosting servers. So if you are hosting your database on a cPanel server that you don't have root access to, you could still use it to export more extensive databases.
+
+## Exporting a Database
+
+To export/backup a database, all you need to do is run the following command:
+
+```
+mysqldump -u your_username -p your_database_name > your_database_name-$(date +%F).sql
+```
+
+Note that you need to change the your_database_name with the actual name of your database and the `your_username` part with your existing MySQL username.
+
+Rundown of the arguments:
+
+* `-u`: needs to be followed by your MySQL username
+* `-p`: indicates that you would be prompted for your MySQL password
+* `>`: indicates that the output of the command should be stored in the .sql file that you specify after that sign
+
+You would create an export of your database by running the above command, which you could later use as a backup or even transfer it to another server.
+
+## Exporting all databases
+
+If you have root access to the server, you could use the `--all-databases flag to export all of the databases hosted on the particular MySQL server. The downside of this approach is that this would create one single `.sql` export, which would contain all of the databases.
+
+Let's say that you would like to export each database into a separate .sql file. You could do that with the following script:
+
+```bash
+#!/bin/bash
+
+##
+# Get a list of all databases except the system databases that are not needed
+##
+DATABASES=$(echo "show databases;" | mysql | grep -Ev "(Database|information_schema|mysql|performance_schema)")
+
+DATE=$(date +%d%m%Y)
+TIME=$(date +%s)
+BACKUP_DIR=/home/your_user/backup
+
+##
+# Create Backup Directory
+##
+
+if [ ! -d ${BACKUP_DIR} ]; then
+  mkdir -p ${BACKUP_DIR}
+fi
+
+##
+# Backup all databases
+##
+
+for DB in $DATABASES;
+do
+    mysqldump --single-transaction --skip-lock-tables $DB | gzip > ${BACKUP_DIR}/$DATE-$DB.sql.gz
+done
+```
+
+The script would backup each database and store the .sql dumps in the `/home/your_user/backup` folder. Make sure to adjust the path to your backup folder.
+
+For more information on Bash scripting, check out this [opensource eBook here](https://github.com/bobbyiliev/introduction-to-bash-scripting).
+
+# Automated backups
+
+You can even set a cronjob to automate the backups above; that way, you would have regular backups of your databases.
+
+To do that, you need to make sure that you have the following content in your `.my.cnf` file. The file should be stored at:
+
+```
+/home/your_user/.my.cnf
+```
+
+You should make sure that it has secure permissions:
+
+```
+chmod 600 /home/your_user/.my.cnf
+```
+
+And you should add the following content:
+
+```
+[client]
+user=your_mysql_user
+password=your_mysql_password
+```
+
+Once you have your `.my.cnf` file configured, you set up a cronjob to trigger the mysqldump export of your database:
+
+```
+0 10,22 * * * /usr/bin/mysqldump -u your_username -p your_database_name > your_database_name-$(date +%F).sql
+```
+
+The above would run at 10 AM and 10 PM every day, so you will have two daily database backups.
+
+You can even expand the logic and add a compression step so that the .sql dumps do not consume too much webspace.
+
+## Conclusion
+
+The `mysqldump` is a great tool to easily and quickly backup your MySQL databases.
+
+For more information, you could take a look at the official documentation here:
+
+* [mysqldump](https://dev.mysql.com/doc/refman/8.0/en/mysqldump.html)
+
+This was initially posted [here](https://devdojo.com/bobbyiliev/how-to-exportbackup-a-mysqlmariadb-database-with-mysqldump).