Databases, classes, tables, nope… I don’t get it, do you?

Databases are important for every project, so software isn’t an exception, DB help us create an space where we can keep all the information needed in the implementation of the project.

Now, we know how to plan a project, how to represent and model it, but if we want to create spaces for information that will help us later, how can we create them and translate them to tables in a DB?

Photo by Christina Morillo on

First we need to take our classes in UML and determine the data we need for each one of them, once we know what we want, we will need to start asking questions about DB creation.

Use the preferred tools for DB and start creating tables for each class and make sure each one has the rows and columns for the information, also check the data types of every space in it.

Photo by Pixabay on

Let’s talk about mapping now, what is it? Agiledata says “it is the act of determining how objects and their relationships are persisted in permanent data storage, in this case relational databases”.  

As we said before, when learning how to map objects to relational databases the place to start is with the data attributes of a class.  An attribute will map to zero or more columns in a relational database.

Here’s an example of mapping:

Now we can learn about it with a video:

Non-relational databases?

Thanks for learning with us, keep it going.


Deja un comentario

Introduce tus datos o haz clic en un icono para iniciar sesión:

Logo de

Estás comentando usando tu cuenta de Cerrar sesión /  Cambiar )

Google photo

Estás comentando usando tu cuenta de Google. Cerrar sesión /  Cambiar )

Imagen de Twitter

Estás comentando usando tu cuenta de Twitter. Cerrar sesión /  Cambiar )

Foto de Facebook

Estás comentando usando tu cuenta de Facebook. Cerrar sesión /  Cambiar )

Conectando a %s

Crea tu página web en
Empieza ahora
A %d blogueros les gusta esto: