[
https://issues.jboss.org/browse/JBIDE-22071?page=com.atlassian.jira.plugi...
]
Koen Aers commented on JBIDE-22071:
-----------------------------------
[~gastaldi] The purpose of the JDBCMetaDataConfiguration is indeed to read all the
mappings from the database and not only the table names. Your workaround is a correct
approach IMO. I'm not sure if anything needs to be done still for this?
JDBCMetaDataConfiguration should allow fetching of table names only
-------------------------------------------------------------------
Key: JBIDE-22071
URL:
https://issues.jboss.org/browse/JBIDE-22071
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: hibernate
Environment: Hibernate Tools 4.3.1.Final
({{org.hibernate:hibernate-tools:4.3.1.Final}})
Reporter: George Gastaldi
Assignee: Koen Aers
Fix For: 4.4.0.Alpha3
I have a MySQL DB containing 40 tables. When I call
{{org.hibernate.cfg.JDBCMetaDataConfiguration.readFromJDBC()}} it takes a considerably
amount of time (minutes) when all I need are the table names. It seems that this method
reads the entire mapping structure for all tables.
This is where I am using it:
https://github.com/forge/core/blob/master/database-tools/impl/src/main/ja....
The {{HibernateToolsHelper}} class calls {{JDBCMetaDataConfiguration.readFromJDBC()}}
here:
https://github.com/forge/core/blob/master/database-tools/impl/src/main/ja...
Can we improve this class to return only the table names and avoid this extra amount of
work?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)