Book Image

Developing Robust Date and Time Oriented Applications in Oracle Cloud

By : Michal Kvet
Book Image

Developing Robust Date and Time Oriented Applications in Oracle Cloud

By: Michal Kvet

Overview of this book

Proper date and time management is critical for the development and reliability of Oracle Databases and cloud environments, which are among the most rapidly expanding technologies today. This knowledge can be applied to cloud technology, on premises, application development, and integration to emphasize regional settings, UTC coordination, or different time zones. This practical book focuses on code snippets and discusses the existing functionalities and limitations, along with covering data migration to the cloud by emphasizing the importance of proper date and time management. This book helps you understand the historical background and evolution of ANSI standards. You’ll get to grips with data types, constructor principles, and existing functionalities, and focus on the limitations of regional parameters and time zones, which help in expanding business to other parts of the world. You’ll also explore SQL injection threats, temporal database architecture, using Flashback Technology to reconstruct valid database images from the past, time zone management, and UTC synchronization across regions. By the end of this book, you’ll be able to create and manage temporal systems, prevent SQL injection attacks, use existing functionalities and define your own robust solutions for date management, and apply time zone and region rules.
Table of Contents (26 chapters)
1
Part 1: Discovering Oracle Cloud
4
Part 2: Understanding the Roots of Date and Time
7
Part 3: Modeling, Storing, and Managing Date and Time
12
Part 4: Modeling Validity Intervals
17
Part 5: Building Robust and Secure Temporal Solutions
20
Part 6: Expanding a Business Worldwide Using Oracle Cloud

Modeling temporal validity using Oracle Database’s embedded PERIOD

The original concept of the PERIOD data type was specified in the temporal paradigm definition, but it was not, however, completely accepted. The principle was based on providing an extra data type covering the duration, internally modeled by the beginning and end points of the state validity. It was based on direct mapping and comparison; thus, the positional relationships were assumed to be widespread. Thanks to that, sorting the states over the evolution was easy, and there was an emphasis on the consistency of the duration and the definition – the beginning point was placed before the end point. It was primarily designed for validity management, but any time frame could be used generally. Since the standardization process did not approve the concept of the PERIOD data type, many research and development prospects were either refused or at least not further developed. As a result, individual developers...