Skip to content

Conversation

@tnazare
Copy link

@tnazare tnazare commented Feb 23, 2016

add DialectHelper to handle uppercase. For now it is very short but I think it can became an entry point to select dialect strategy.

Add a non-standard entry point keyword "using" in Assertions.

By default, assertj-db is still upper-casing every column name

See #32 #31

add DialectHelper to handle uppercase. For now it is very short but I think it can became an entry point to select dialect strategy. Add a non-standard entry point keyword "using" in Assertions By default, assertj-db is still upper-casing every column name
@regis1512
Copy link
Member

I will try to see that tonight.
Thanks

@regis1512
Copy link
Member

I saw that idea.
It is a good idea which make an answer in some cases.

But i think there are more case :

  • the user can consider the name of tables, the name of columns and the name of primary keys
  • he can want to compare the names with the case or ignore it
  • he can want to have the name exactly like given by the metadata of the database or transform with upper or lower case

So to take more case, i have implemented new classes : LetterCase and all associated classes (especially SourceWithLetterCase and DataSourceWithLetterCase).

But thanks for your work, if there was not all these cases i will certainly take your solution.

@regis1512 regis1512 closed this Mar 12, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

2 participants