In my current project, I use a SQL domain to implement the formatting and precedence rules for Semantic Versioning<\/a>. I started with a simple implementation covering only the most basic rules. Getting the sorting right is key in my project. It allows me to identify the latest compatible version of an artefact. After adding some tests I started to evolve the functionality to a point where I can say that the implementation covers everything needed for my use case.<\/p>\n\n\n\n Domains make data models easier to understand and reduce the logic regarding data consistency and visualisation. In this blog post, I demonstrate this by evolving a domain for Semantic Versioning. This should give you an impression of whether keeping domains and table columns in sync is more complicated than traditional approaches.<\/p>\n\n\n\n A data use case domain (aka SQL domain, aka domain) is a new feature in the Oracle Database 23ai based on the SQL standard. Domains abstract column properties so that they can be used across multiple tables. They come in different flavours:<\/p>\n\n\n\n It’s important to notice, that a table column can have only one domain. It is therefore not possible to combine single-column domains with multi-column or flexible domains.<\/p>\n\n\n\n First, let’s create three domains.<\/p>\n\n\n\n2. What Are Domains?<\/h2>\n\n\n\n
\n
3. Starting Model<\/h2>\n\n\n\n
3.1 Domains<\/h5>\n\n\n\n