Switch to: V11V10V9V8V7V6V5

Sakila Database

Overview

The “sakila” sample database was developed by 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 about Sakila database you can find on official site, or download as pdf file.

We have take the “sakila” database, which exists as demo for mySQL, PostgreSQL, SQLite, Oracle and other databases and port it into Valentina DB model. Even more, we provide here 3 variants.

Differences in Databases

In the table below you can see 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, amount of objects is reducing from database with RDB Links to database with ObjPtrLinks and to database with Binary Links. This is a natural consequence of using Valentina's ObjPtr & Binary Links. Except showed objects, the number of fields in tables was reduced too: for ObjPtr links was removed primary key fields from the referenced tables, and for Binary Links was removed references fields (Foreign Keys or ObjPtr). In result, from database was removed sequences, and alot of indexes. For database with binary links also was removed tables used for realization M:M relationship.

You can see difference in the database schemas on below pictures, 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