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

Optimizers cannot optimize columns with certain TypeMapper:s #452

Closed
minborg opened this issue May 17, 2017 · 0 comments
Closed

Optimizers cannot optimize columns with certain TypeMapper:s #452

minborg opened this issue May 17, 2017 · 0 comments
Assignees
Labels
Milestone

Comments

@minborg
Copy link
Contributor

minborg commented May 17, 2017

If a column has a TypeMapper that does not preserve the order between the original database type and the Java type, then an Optimizer cannot render the column to an ORDER BY operation directly.

The same problem will occur for certain filters (e.g. .greaterThen()) where the order is not retained over the TypeMapper. So these particular operations cannot be rendered to a WHERE statement.

There must be a way for an Optimizer to know if a TypeMapper preserves order.

It could be possible to describe a SQL mapping to apply, so that the order could be retained. However, it is difficult in the general case.

@minborg minborg added the bug label May 17, 2017
@minborg minborg self-assigned this May 17, 2017
@minborg minborg added this to the 3.0.10 Forest milestone May 17, 2017
minborg added a commit that referenced this issue May 26, 2017
@minborg minborg closed this as completed May 26, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant