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.

Sign up for GitHub

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

Jump to bottom

When using options manager the internal field type is stored as varchar(255) #1507

Closed
Toflar opened this issue Aug 12, 2015 · 3 comments
Closed

When using options manager the internal field type is stored as varchar(255) #1507

Toflar opened this issue Aug 12, 2015 · 3 comments
Labels
bug
Milestone
2.3.0

Comments

@Toflar
Copy link
Member

Toflar commented Aug 12, 2015

I don't think this is intentional, is it? When the optionsSource is a table then it's always an integer which would probably optimize the key which is added on filterable fields :)
@aschempp aschempp added the bug label Aug 13, 2015
@aschempp aschempp added this to the 2.3.0 milestone Aug 13, 2015
@aschempp
Copy link
Member

that key is only for the backend list as far as I know?

@Toflar
Copy link
Member Author

Toflar commented Aug 13, 2015

It's only about the field type that should be an integer ;)

aschempp added a commit that referenced this issue Aug 18, 2015
@aschempp
Optimize SQL field types (#1507)
3c3ea50
@aschempp
Copy link
Member

Fixed in 3c3ea50

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
2.3.0
Development

No branches or pull requests
2 participants
@Toflar @aschempp