-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issue #212: Implemented enums in database #300
base: 5.0
Are you sure you want to change the base?
Conversation
Signed-off-by: alexmerlin <[email protected]>
Signed-off-by: alexmerlin <[email protected]>
Signed-off-by: alexmerlin <[email protected]>
Signed-off-by: alexmerlin <[email protected]>
@arhimede @MarioRadu @pinclau Found the issue... |
But why that is an issue ? |
Signed-off-by: alexmerlin <[email protected]>
Correction: It was this old hack we added ages ago. |
One small issue to note: in the migration, the |
Signed-off-by: alexmerlin <[email protected]>
@MarioRadu @pinclau If you have time to take a look at this PR, it would be helpful.
I followed the same steps as with dotkernel/api#339 but can't figure out what is missing.
The issue is the the same we had before when we tried implementing enums.
Running the command:
will create a new migration even if there were no changes in the entities, with this
up()
:and
down()
:Emptying Doctrine cache did not solve the problem.
Any feedback is welcomed!