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

Disable toUpperCase on table name #32

Closed
glefloch opened this issue Feb 2, 2016 · 5 comments
Closed

Disable toUpperCase on table name #32

glefloch opened this issue Feb 2, 2016 · 5 comments
Labels

Comments

@glefloch
Copy link

glefloch commented Feb 2, 2016

Hi,

When I try to use asserJ-db, all query to database use uppercase table nam,w hich is actually not working with our curretn Mysql configuration.
I know I can allow it in the my.cnf configuration file. But on some environment this is impossible.
I that possible to a setter to disable it?

Regards

@tnazare
Copy link

tnazare commented Feb 23, 2016

Hi,

I have the same problem...
Any news on this issue?

Thib.

@glefloch
Copy link
Author

Unfortunately no...

@tnazare
Copy link

tnazare commented Feb 23, 2016

#33

@regis1512
Copy link
Member

Sorry to have be long to implement a solution.
You can now find new classes : LetterCase and all associated classes (especially SourceWithLetterCase and DataSourceWithLetterCase) which are here to fix this problem.

When you instantiate a SourceWithLetterCase or DataSourceWithLetterCase, you can indicate the behavior (the conversion like upper and lower and the comparison) with the letter case of the tables, columns and primary keys.
I hope that with this flexibility that all the users can find a compatible solution with their database.
Please note that the solution is extensible because LetterCase use CaseComparison and CaseConversion which are interfaces.

@regis1512
Copy link
Member

And thank to tnazare for his proposition

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

3 participants