Mega Creative uses five lookup tables to normalize repeated values across the database. These tables are seeded at setup time and referenced by foreign keys on student and program records. None of the five tables store timestamps — each model setsDocumentation Index
Fetch the complete documentation index at: https://mintlify.com/keving5726/megacreative/llms.txt
Use this file to discover all available pages before exploring further.
public $timestamps = false — keeping them lean and read-friendly in query results.
Statuses
Two values shared by both students and programs:
Habilitado and Inhabilitado.Sex Options
Two values for student sex:
Masculino and Femenino.Countries (Paises)
30 Faker-generated country records seeded at startup.
States & Cities
50 Faker-generated states and 50 cities forming a three-tier geographic hierarchy.
Statuses
Thestatuses table is seeded by StatusesTableSeeder and contains exactly two rows. The same rows are reused as the status_id foreign key on both the carreras table and the estudiantes table.
| id | status | Meaning |
|---|---|---|
| 1 | Habilitado | Record is active / enabled |
| 2 | Inhabilitado | Record is inactive / disabled |
Status model maps to the statuses table and carries no timestamps:
Sex Options
Thesexos table is seeded by SexosTableSeeder and contains exactly two rows. The field name in the table is tipo, which the create/edit Blade views render directly in the dropdown option labels.
| id | tipo |
|---|---|
| 1 | Masculino |
| 2 | Femenino |
Sexo model maps to the sexos table:
Geographic Data
Three tables form a simple three-tier location hierarchy. Each table exposes anombre column that the Blade dropdowns display. All three models set public $timestamps = false.
| Table | Model | Rows seeded | Seeder class |
|---|---|---|---|
paises | Pais | 30 | PaisesTableSeeder |
estados | Estado | 50 | EstadosTableSeeder |
ciudades | Ciudad | 50 | CiudadesTableSeeder |
All geographic records are populated with Faker-generated dummy values and
do not represent real countries, states, or cities. For a production deployment
you should replace the factory-based seeders with real geographic data — for
example, sourced from an ISO 3166 dataset or a reputable geocoding API — and
update the factory definitions accordingly.
How They Are Seeded
DatabaseSeeder::run() calls all seeders in dependency order. Statuses and sex options come first because programs and students reference them. Geographic tables are populated before students because student records require valid pais_id, estado_id, and ciudad_id values.