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

Control over data types and sizes #20

Open
EnriqueL8 opened this issue Mar 9, 2018 · 1 comment
Open

Control over data types and sizes #20

EnriqueL8 opened this issue Mar 9, 2018 · 1 comment
Labels
enhancement New feature or request

Comments

@EnriqueL8
Copy link
Contributor

EnriqueL8 commented Mar 9, 2018

A way of specifying the data types used in the database for the model.

@kilnerm kilnerm added the enhancement New feature or request label Nov 19, 2018
@xeokeri
Copy link

xeokeri commented Dec 3, 2018

I agree with this. I have an enum that subclasses string, but it should be a varchar or char, instead it creates text, but then has issues with the enum class when doing additional QueryParam filtering. As it doesn't see the Enum : String, but as an default and converting to String. Having more fine grain control over it would also assist with the MySQL bind issue I'm having locally trying to find a work-around on this in the meantime.

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

No branches or pull requests

3 participants