EF Core Migrations History — Tienda Mi Cholo Schema

Tienda Mi Cholo uses EF Core’s code-first migration system to version-control every schema change. Each migration is a timestamped C# class in the Final_proyecto.Migrations namespace that contains Up() (apply) and Down() (rollback) methods generated by the EF Core tooling. Three migrations bring the database from nothing to the current production schema. The migration history is stored in the __EFMigrationsHistory table that EF Core maintains automatically in TIENDA_MICHOLO.

Always commit migration files to source control alongside the model changes that produced them. Migrations are the authoritative record of how the schema evolved and are required to reproduce the database on any new environment.

Running Migrations

To apply all pending migrations and bring the database up to date:

dotnet ef database update

Run this command from the project directory (where Final proyecto.csproj is located) after cloning the repository or pulling new migration files.

Migration History

Migration 1 — Inicial

Timestamp: 20260706200951
Class: Inicial This is the foundational migration. It creates all seven application tables from scratch, establishes every foreign key constraint and index, and seeds the reference data the application requires before first use.

Show Tables created

Table	Key column(s)	Notes
`Categorias`	`ID_Categoria` (identity)	`nvarchar(50)` name, `nvarchar(200)` description
`Clientes`	`ID_Cliente` (identity)	`nvarchar(50)` nombres/apellidos, `nvarchar(11)` document
`Roles`	`ID_Rol` (identity)	`nvarchar(50)` name
`Productos`	`ID_Producto` (identity)	`decimal(10,2)` prices, `int` stock, FK to Categorias
`Usuarios`	`ID_Usuario` (identity)	`bit` Estado, FK to Roles (cascade)
`Ventas`	`ID_Venta` (identity)	`decimal(10,2)` total, FK to Clientes (cascade)
`DetalleVentas`	`ID_DetalleVenta` (identity)	FK to Ventas (cascade) + FK to Productos (cascade)

Show Seed data inserted

3 roles:

ID_Rol	NomRol
1	Administrador
2	Gerente
3	Cajero

1 admin user:

Field	Value
ID_Usuario	1
NomCompleto	Administrador del Sistema
NomUsuario	admin
CorreoUsuario	admin@micholo.com
Contraseña	admin123
Estado	true
Rol_ID	1 (Administrador)

1 default client (Público General):

Field	Value
ID_Cliente	1
Nombres	Público
Apellidos	General
TipoDocumento	DNI
NumeroDocumento	00000000
Telefono	900000000
Correo	publico@general.com
Direccion	Tienda Principal

6 product categories:

ID	NombreCategoria	Descripcion
1	Lácteos	Leche, queso, yogurt y derivados
2	Bebidas	Gaseosas, jugos, agua y bebidas
3	Snacks	Galletas, papas, dulces y golosinas
4	Limpieza	Detergentes, lejía, jabones
5	Abarrotes	Arroz, azúcar, aceite, fideos
6	Frutas y Verduras	Productos frescos del día

Migration 2 — AddEstadoToProducto

Timestamp: 20260707002811
Class: AddEstadoToProducto Adds the Estado column to the Productos table so individual products can be marked active or inactive without being deleted. Change applied:

migrationBuilder.AddColumn<bool>(
    name: "Estado",
    table: "Productos",
    type: "bit",
    nullable: false,
    defaultValue: false);

Column	Type	Nullable	Default
`Estado`	`bit`	NOT NULL	`false` (0)

The column is added with a default of false. After applying this migration you should update any existing products to Estado = true if they are intended to be available for sale. The POST /Producto/Nuevo action always sets Estado = true for new products created through the UI.

Rollback (Down): Drops the Estado column from Productos.

Migration 3 — MakeClienteFieldsNullable

Timestamp: 20260707011120
Class: MakeClienteFieldsNullable Makes Correo and Direccion nullable on Clientes, and also makes Descripcion nullable on Productos. This allows client records to be created without an email address or physical address — important for the boleta flow where the sale controller creates client records on the fly with minimal information. Changes applied:

Table	Column	Old Type	New Type
`Clientes`	`Correo`	`nvarchar(100)` NOT NULL	`nvarchar(100)` NULL
`Clientes`	`Direccion`	`nvarchar(200)` NOT NULL	`nvarchar(200)` NULL
`Productos`	`Descripcion`	`nvarchar(200)` NOT NULL	`nvarchar(200)` NULL

migrationBuilder.AlterColumn<string>(
    name: "Correo",
    table: "Clientes",
    type: "nvarchar(100)",
    maxLength: 100,
    nullable: true, ...);

migrationBuilder.AlterColumn<string>(
    name: "Direccion",
    table: "Clientes",
    type: "nvarchar(200)",
    maxLength: 200,
    nullable: true, ...);

migrationBuilder.AlterColumn<string>(
    name: "Descripcion",
    table: "Productos",
    type: "nvarchar(200)",
    maxLength: 200,
    nullable: true, ...);

Rollback (Down): Reverts all three columns to NOT NULL with an empty-string default ("").

Creating New Migrations

After modifying a model class or the AppDbContext, generate a new migration and apply it:

dotnet ef migrations add <MigrationName>
dotnet ef database update

Follow the existing naming convention: use descriptive PascalCase names that describe the schema change (e.g., AddTelefonoToUsuario, RenameProductoColumns).

Rolling back the Inicial migration (running dotnet ef database update 0) drops all seven tables and all data, including the seed roles, admin user, default client, and categories. The tables and seed data are recreated the next time dotnet ef database update is run, but any transactional records (sales, custom products, additional users) will be permanently lost.

Data Models

Controllers

Database

EF Core Migrations History — Tienda Mi Cholo Schema

Running Migrations

Migration History

Migration 1 — Inicial

Migration 2 — AddEstadoToProducto

Migration 3 — MakeClienteFieldsNullable

Creating New Migrations

Build docs developers (and LLMs) love

Data Models

Controllers

Database

Documentation Index

​Running Migrations

​Migration History

​Migration 1 — Inicial

​Migration 2 — AddEstadoToProducto

​Migration 3 — MakeClienteFieldsNullable

​Creating New Migrations

Build docs developers (and LLMs) love

Running Migrations

Migration History

Migration 1 — Inicial

Migration 2 — AddEstadoToProducto

Migration 3 — MakeClienteFieldsNullable

Creating New Migrations