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

[DbOom] DefaultResultSetMapper not support dynamic tableName #97

Closed
zqq90 opened this issue Mar 21, 2014 · 1 comment
Closed

[DbOom] DefaultResultSetMapper not support dynamic tableName #97

zqq90 opened this issue Mar 21, 2014 · 1 comment
Labels

Comments

@zqq90
Copy link
Member

zqq90 commented Mar 21, 2014

Since DefaultResultSetMapper#createTypesTableNames(Class[] types) used tableNames from DbEntityDescriptor directly.
Finally, I override this method, used custom table names refer to DefaultResultSetMapper#tableNames ,it works 😄 , just wanna you know this.

@zqq90 zqq90 changed the title [DbOom] DefaultResultSetMapper not support dynamic tableName、 [DbOom] DefaultResultSetMapper not support dynamic tableName Mar 21, 2014
@igr igr added this to the 3.5.2 milestone Mar 21, 2014
@igr igr self-assigned this Mar 21, 2014
@igr igr closed this as completed Jun 25, 2014
@igr igr reopened this Jun 25, 2014
@igr igr removed this from the 3.5.2 milestone Jun 27, 2014
@igr igr removed their assignment Jun 28, 2014
@igr igr added backlog and removed todo labels Jul 4, 2014
@igr
Copy link
Member

igr commented Feb 1, 2015

Closing as backlog.

@igr igr closed this as completed Feb 1, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Development

No branches or pull requests

2 participants