Skip to content
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

incorrectDefaults in SchemaUtils is always true for nullable columns without exposed defaults in MySQL/MariaDB #1457

Closed
spand opened this issue Feb 16, 2022 · 0 comments · Fixed by #2136

Comments

@spand
Copy link
Contributor

spand commented Feb 16, 2022

The cause is that nullable columns are always implicitly default null. I am not sure what this should mean in terms of Exposed. The question is then

  1. Should exposed be aware of this limitation in MySQL/MariaDB and consider nullable exposed columns without default values the same as columns with default null ?
  2. User error. User should not declare tables in exposed that cannot be expressed by the underlying database.

Thoughts?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants