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

What timepoint means and how to use it

The moment in time is characterized by only one value expressing validity. It can be used to model either one timepoint or the start point of the duration. If the timepoint represents only one value, it must be ensured that a new state is inserted for each moment, regardless of the change. For example, a new data image must be entered into the database every month if monthly granularity is used. The management of the system is controlled by a plan (calendar) of events, which occurs periodically. These systems are suitable for obtaining a slice (image) of data in precisely defined periods but without further analysis of the changes in individual attributes. This limitation is just related to storage demands. Data is stored periodically, irrespective of the real change. As a result, many duplicates can be present. Expressing the duration by the end point is uncommon as it can be unknown or not very precise. People usually don’t know in advance...