Larry, > In my experience, Hibernate works best when two criteria are met: > 1) You are creating a database for a specific purpose, from scratch > 2) You are creating the ONLY application that will access that database
I disagree with this and recommend you post this statement on forums.hibernate.org. I'm sure you'll get plenty of answers to the contrary. > The time to draw that screen changed from over 10 > minutes (we killed it after that, and are not > sure how long it would have run unchecked) Did you bother doing one of the following: 1) Check your SQL server logs to see what exact statement was being executed? You could have tuned your query using hibernate's SQL shortcut language OR used a native SQL call (method names I cannot recall at this moment because I use HSQL). The native SQL calls can be invoked in both the 2.1.X series AND the 3.0 rc sets of releases. You can also see the SQL query by setting "show_sql=true" in your hibernate.properties or hibernate.cfg.xml files to have the generated SQL query get printed to your application log. 2) Make sure your connection properties were set properly? 3) Enable lazy loading as necessary to reduce database joins and calls? 4) Request cache tweaking assistance by posting your scenario and caching ideas to forums.hibernate.org for feedback from those highly experienced in using caching with Hibernate? There could have been "quirks" to the version of caching you were using or HOW you configured caching. Regards, David, a happy hibernate user --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
