[
http://opensource.atlassian.com/projects/hibernate/browse/HBX-812?page=co...
]
Syd Poetry commented on HBX-812:
--------------------------------
45 tables or so. it used to take 1-2 seconds, not long at all. I ran the update software
which updated several components. I added a new table, went to regenerate the mapping
files, stubs, and boom, 4-5 minutes. It sticks (on the reveng.xml) "Fetching
children of database". Went it does finally respond, the root element is
"undefined", with the table names listed (properly)underneath it. The database
itself is quite responsive when using other tools (not related to Java/Eclipse). So
I'm pretty sure its not a DB or system resources issue. Restarted hoping that might
clear it, but still no go (4-5 minutes on refresh). *Anything* from the Hibernate tools
code that access the jdbc meta-data gets stuck on reading the JDBC Metadata. I switched
from the MYSQL 3.13 connecter to MYSQL 5.0 jdbc connecter hoping it was an incompatibility
with 3.13 that was causing the problem, but no appreciable improvement.
Fetching Children of Database _crawls_.
---------------------------------------
Key: HBX-812
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HBX-812
Project: Hibernate Tools
Type: Bug
Components: reverse-engineer
Versions: 3.2beta8
Environment: MySQL 5.0, Eclipse 3.2, JDK 1.5, Beta8 for Hibernate Tools
Reporter: Syd Poetry
I just updated a bunch of components for Eclipse (mostly related to Visual Editor); added
a couple of tables to my database, went to regenerate all the POJO clases .hbm.xml mapping
files, and found that anything that queries the database schema runs abysmally slow.
Updated the tools from beta6 to beta8 thinking it might be a conflict with one of the
updates that was performed, still very slow (5+ minutes to retrieve a list of tables!).
Deleted all my hibernate-related XML files thinking it might be a parsing error, went to
generate a new console file, and revenge.xml, found out that any listbox that tried to
access the schema appeared to be hanging. It finishes after much hard-drive crunching. I
have 2.2 GBs free running windows XP, MEM usage is 856 MB out of 1.5 GB physical memory.
Just out of curiousity, is *anyone* else having this slow response for schema detection?
I'm wondering if I have to update another component like a driver or something like
that.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira