MySQL 8.0: From SQL Tables to JSON Documents

 MySQL 8.0: From SQL Tables to JSON Documents


One of the nice things about MySQL 8.0 is the ability to combine the relational and document models. As a developer, you can choose to work with traditional SQL tables, with schemaless JSON documents, or with both types at the same time. Here we show how to bridge SQL tables and JSON documents by using JSON functions. Enjoy!


Step.1.Create sample database.


step.2.create table insert record.

step.3.From an SQL Table to a JSON Document


Here we use two JSON aggregation functions called JSON_ARRAYAGG() and JSON_OBJECT(). We simply select from employees and convert the result set into JSON like this:


step.4.We now have a JSON Document referenced by the variable @jsonempl. Let us look at it using the JSON_PRETTY() function:



step.5. Now sql also.







Comments

Post a Comment

Popular posts from this blog

MySQL Replication Switchover: Step-by-Step Guide

Image
 MySQL Replication Switchover: Step-by-Step Guide MySQL replication is a powerful feature that allows you to create redundant copies of your database for improved availability and scalability. In certain scenarios, it becomes necessary to switch the roles of the master and slave servers in a replication setup. This article will guide you through the process of performing a MySQL replication switchover, ensuring a smooth transition without any data loss. Let’s dive into the step-by-step instructions. I have tow node one is master node and another is slave node.Given below details:- Current Master: 192.168.70.10 Current Slave : 192.168.70.11 Verifying the Replication:- Before initiating the switchover, it’s important to verify that replication is functioning correctly on the current Slave server (192.168.70.11). Execute the following queries to ensure the replication status: mysql> show slave status\G This command displays the slave’s status, including information such as replicat...
Read more

How to create database manually in oracle 11g R2

step.1.go to the cat /etc/oratab and edit it. vi /etc/oratab pankaj:/u01/app/oracle/product/11.2.0/dbhome_1:N step.2.login to oracle user [oracle@servera ~]$ . oraenv ORACLE_SID = [orcl] ? pankaj The Oracle base for ORACLE_HOME=/u01/app/oracle/product/11.2.0/dbhome_1 is /u01/app/oracle note:-. oraenv command hit for oratab and pankaj is name of the database. step.3.copy pfile cd /u01/app/oracle/product/11.2.0/dbhome_1/dbs [oracle@servera dbs]$ cp initorcl.ora initpankaj.ora step.4.edit pfile current pfile orcl.__db_cache_size=289406976 orcl.__java_pool_size=4194304 orcl.__large_pool_size=4194304 orcl.__oracle_base='/u01/app/oracle'#ORACLE_BASE set from environment orcl.__pga_aggregate_target=310378496 orcl.__sga_target=457179136 orcl.__shared_io_pool_size=0 orcl.__shared_pool_size=150994944 orcl.__streams_pool_size=0 *.audit_file_dest='/u01/app/oracle/admin/orcl/adump' *.audit_trail='db' *.compatible='11.2.0.0.0' *.con...
Read more

How To Install and Configure Innodb Cluster /shell/Router

 InnoDB Cluster InnoDB Cluster = MySQL Server + MySQL Shell + MySQL Router  MySQL InnoDB has three major components: 1. MySQL group replication :–  It is a group of database servers. It replicates the MySQL databases across the multiple nodes, and it has fault tolerance. When changes in the data occur in the MySQL databases, it automatically replicates to the secondary nodes of the server. The concept of the MySQL group replication is similar to the concept of the AlwaysOn availability group. 2. MySQL Router: –  When a failover occurs, the client application must be aware of the PRIMARY instance and cluster topology. This functionality is handled by the MySQL Router. It routes that redirects the data requests to the available MySQL Server instance.MySQL Router acts as a proxy that is used to hide the multiple MySQL database servers. The concept of the MySQL Router is similar to the Virtual network name of the Windows Server failover cluster. 3. MySQL Shell :–  I...
Read more