JSON in 18c/19c: JSON as it was Meant to be
Stew Ashton, Independent
JSON was originally designed as a "lightweight data-interchange format" between programs, not a way to store data. With new JSON enhancements in version 18c/19c, SQL is now a full-service language for exchanging relational data in JSON format: extracting data in JSON format for sending, and transforming received JSON into relational data for storing. We will see how JSON simplifies the classic globalisation problems of data exchange (character sets, formats, time zones, etc.) and how the SQL/JSON functions help ease the transition between two organisations of data: rows and columns in SQL vs. structures and arrays in programming languages. This session will demonstrate the use of JSON for data exchange in large volumes, in comparison with other file-based formats. It will also present the advantages of JSON as a format for "transactional APIs" that implement the "Smart Database" paradigm. Attendees will learn how to extract fully read-consistent data from any combination of tables into JSON; how to transform even complex JSON into relational format; and how the JSON format can ease communication between the database and calling applications.
Stew is one of the top SQL developers in the Oracle community, to which he has contributed for over a decade through the AskTom site, the OTN forum dedicated to SQL and PL/SQL, and his blog. He is also an award-winning conference speaker and an Oracle Ace.Stew has been a developer and application architect for 35 years, working in mainframe, client-server and web architectures. Since 2005 he has focused on proper use of the Oracle database in OLTP applications and batch processing, improving performance up to 300-fold.