Oracle Visual Builder: Applications That Outlive Their First Release · Module 5 · Data: business objects and external services
Designing a business object
Lesson 47 of 176 · 3 min
Fields, types and relationships, and THE FIELD YOU WILL WISH YOU HAD ADDED BEFORE THERE WERE ROWS. Designing one of these is ordinary data modelling, and the only thing that makes it worth a lesson is how easy the tool makes it to skip that step entirely. TYPES FIRST, AND THE MISTAKE IS ALWAYS THE SAME: EVERYTHING BECOMES TEXT. A date as text does not sort, a number as text does not add up, and a boolean as text acquires a third value the day somebody writes "Y". The tool will let you, and changing a column's type once there are rows is a migration rather than an edit. RELATIONSHIPS NEXT, AND THE QUESTION NOBODY ASKS IS WHAT A DELETE MEANS. Rows point at other rows; deleting the target either cascades, is refused, or leaves a reference to nothing. All three are legitimate and the wrong one is discovered by…
The full lesson is part of the course
The video, the complete written lesson and the module quiz are included in Oracle Visual Builder: Applications That Outlive Their First Release, with a certificate on completion and a fourteen-day refund window.
In this module: Module 5 · Data: business objects and external services
- 1Business objects: your own database
- 2When to keep data here, and when not to
- 3Designing a business object
- 4Object rules and triggers
- 5Importing and exporting data
- 6The endpoints your objects expose
- 7External services: the other half
- 8Reference data and lookups
- 9What breaks: three data failures
- 10Lab briefing · Two sources, one screen