Skip to content

Expose internal enum field types? #108

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

Open
bckohan opened this issue Mar 21, 2025 · 0 comments
Open

Expose internal enum field types? #108

bckohan opened this issue Mar 21, 2025 · 0 comments
Labels
question Further information is requested
Milestone

Comments

@bckohan
Copy link
Member

bckohan commented Mar 21, 2025

EnumField will automatically trigger migrations when the underlying enum changes in such a way that the database needs alterations (mostly column size overflows).

Some users may want to more explicitly specify the enum type - say use EnumPositiveSmallIntegerField directly instead of relying on EnumField to resolve it.

EnumPositiveSmallIntegerField should still update check constraints automatically when necessary.

This may just involve adding these types to __all__ and documenting this usage...

@bckohan bckohan added the question Further information is requested label Mar 21, 2025
@bckohan bckohan added this to the 2.3 milestone Mar 27, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

1 participant