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

Generating random dates

When dealing with date management and testing, a crucial task is associated with generating dates. Based on my experience in business, it is inevitable to focus on relevance and correctness. Each date consists of day, month, and year elements. There is also time denotation, but it can be ignored in this phase.

I often encounter my students modeling individual elements separately, and then the resulting value is achieved by putting the elements together. However, how do you generate and process it? No problem – the year can be defined by the range to be generated. The same approach can be applied to month reflection. However, to ensure overall consistency, the day elements must be emphasized. Namely, what about the right border for day processing? Some months have 31 days. The rest have only 30 days. Moreover, there is a specific month (February) with a different number of days. It consists of either 28 or 29 days (if it’s a leap year). The processing...