Redesign TableManipulation in JDBC cache loader
Issue Type: Task
Components: Loaders and Stores
Reporter: Trustin Lee
Assignee: Manik Surtani
Fix For: 5.0.0.BETA1, 5.0.0.Final
There are two on-going issues related with TableManipulation at the moment: ISPN-686 and
ISPN-698. They both are related with vendor specific behavior, and the current
implementation uses switch-cases to deal with the differences between vendors. Could we
instead use inheritance to make the code look cleaner and easier to maintain? Hibernate
Also, the properties like custom types, names, prefixes, fetch/batch sizes could be moved
to AbstractJdbcCacheStoreConfig (or its subclass because we have mixed JDBC store) instead
of exposing TableManipulation directly to a user.
Since Hibernate already provides very well defined dialect metadata model, we could simply
tap into it. However, we should wrap it with a simple wrapper class so that a user can
configure the JDBC store without the knowledge of Hibernate.
This is a backward incompatible change - will be done in 5.0, and TableManipulation and
its related methods should be deprecated in 4.2.
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see: http://www.atlassian.com/software/jira