Switch to: V9V8V7V6V5

Sakila Database

The “sakila” sample database was developed by the MySQL AB documentation team, under the BSD license, and is intended to provide a standard schema that can be used for examples in books, tutorials, articles, samples, and so forth. The original documentation for the Sakila database can be found on theofficial site, or downloaded as a pdf file.

Overview

We took the Sakila database which exists as a demo for mySQL, PostgreSQL, SQLite, Oracle and other databases) and ported it into Valentina DB model and made it available in three variants.

Differences in Databases

In the table below you can see the amount of objects in each database:

Schema Objects with RDB Linkswith ObjPtr Linkswith Binary Links
Columns 98 75 51
Diagrams 2 2 2
Indexes 43 27 4
Links 22 22 20
Procedures 5 5 5
Properties 0 0 0
Sequences 13 0 0
Tables 16 16 14
Triggers 17 17 15
Types 1 1 1
Views 5 5 5

You can see that the number of objects are fewer from databases with RDB Links to databases with ObjPtrLinks and even fewer in databases with Binary Links. This is a natural consequence of using Valentina's ObjPtr & Binary Links.

Except showed objects, the number of fields in tables were reduced. ObjPtr links allowed removal of primary key fields from the referenced tables, and Binary Links allowed removal of references fields (Foreign Keys or ObjPtr). This result was removal of many sequences and indexes. Binary links also allowed removal of tables no longer needed for M:M relationship.

Compare the differences in the database schemas, or in the diagram “Films” in each database:

Diagram for DB with RDB Links

Diagram for DB with ObjPtr Links

Diagram for DB with Binary Links

In result of deleting unused fields, the actual size of stored data is reduced:

with RDB Linkswith ObjPtr Linkswith Binary Links
Size (Kb) 6079 5833 4924