|
|
1 year ago | |
|---|---|---|
| .. | ||
| K8S | 1 year ago | |
| servicios | 1 year ago | |
| .gitignore | 1 year ago | |
| Pipfile | 1 year ago | |
| Pipfile.lock | 1 year ago | |
| README.md | 1 year ago | |
https://stackoverflow.com/questions/62640576/flask-migrate-valueerror-constraint-must-have-a-name
Cada vez que se haga un cambio en la bd
From this point on you have a project that is fully enabled to use database migrations. The normal migration process goes as follows:
- You will make some changes to your models in your Python source code.
- You will then run flask db migrate to generate a new database migration for these changes.
- You will finally apply the changes to the database by running flask db upgrade.
This cycle repeats every time new changes to the database schema are needed.
con lo anterior queda creada la base de datos.
Insertar los ficheros SQL con:
sqlite3 repostajes.db < vehiculos.sql sqlite3 repostajes.db < repostajes.sql
¡ojo! estos ficheros son un volcado de mysql. Hay que 'tocarlos' para ajustarse al nuevo modelo. Los que hay aquí ya están adaptados