Search icon
Subscription
0
Cart icon
Close icon
You have no products in your basket yet
Arrow left icon
All Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Newsletters
Free Learning
Arrow right icon
Developing Robust Date and Time Oriented Applications in Oracle Cloud

You're reading from  Developing Robust Date and Time Oriented Applications in Oracle Cloud

Product type Book
Published in May 2023
Publisher Packt
ISBN-13 9781804611869
Pages 464 pages
Edition 1st Edition
Languages
Concepts
Author (1):
Michal Kvet Michal Kvet
Profile icon Michal Kvet

Table of Contents (26) Chapters

Preface 1. Part 1: Discovering Oracle Cloud
2. Chapter 1: Oracle Cloud Fundamentals 3. Chapter 2: Data Loading and Migration Perspectives 4. Part 2: Understanding the Roots of Date and Time
5. Chapter 3: Date and Time Standardization Principles 6. Chapter 4: Concepts of Temporality 7. Part 3: Modeling, Storing, and Managing Date and Time
8. Chapter 5: Modeling and Storage Principles 9. Chapter 6: Conversion Functions and Element Extraction 10. Chapter 7: Date and Time Management Functions 11. Chapter 8: Delving into National Language Support Parameters 12. Part 4: Modeling Validity Intervals
13. Chapter 9: Duration Modeling and Calculations 14. Chapter 10: Interval Representation and Type Relationships 15. Chapter 11: Temporal Database Concepts 16. Chapter 12: Building Month Calendars Using SQL and PL/SQL 17. Part 5: Building Robust and Secure Temporal Solutions
18. Chapter 13: Flashback Management for Reconstructing the Database Image 19. Chapter 14: Building Reliable Solutions to Avoid SQL Injection 20. Part 6: Expanding a Business Worldwide Using Oracle Cloud
21. Chapter 15: Timestamp Enhancements 22. Chapter 16: Oracle Cloud Time Zone Reflection 23. Assessments 24. Index 25. Other Books You May Enjoy

What is temporality?

What does the term temporality mean? Is it the logical concept or the physical model supported by the infrastructure? Or can it just be defined by a set of rules that must be applied? Well, it does not reflect a specific model or implementation. Instead, temporality covers any solution that deals with time. Namely, each object state (data tuple) can be positioned on a timeline. Thus, each object is delimited by multiple states valid during the specified period of time. Generally speaking, relational databases can be automatically considered to be partially temporal, whereas each data change is always encapsulated by the transaction. And each transaction generates data change vectors stored in the transaction logs. So, what does it actually mean? Such a transaction log structure clearly denotes the object state history, doesn´t it? Thus, the transactional databases can produce states valid in the past. However, it is not as simple as it may seem at first glance...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $15.99/month. Cancel anytime}