Refactor migrations to exclude ORM usage, resolving errors caused by … #37
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
…evolving Entity structures
Updated the migration approach to avoid using the ORM, as it was leading to issues when Entity structures were modified. Specifically, when the ORM was used to select data from the database, it triggered errors if a column was missing, yet this column was intended to be added in a subsequent migration. This change ensures more robust and error-free migrations.