On Sun, 13 Mar 2005 09:26:24 -0500, David G. Friedman wrote: > 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. >
Disagree away. I love to disagree with people. That is how I learn. Besides, you are free to be wrong if you want to be. ;-) > > 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. > It was using native SQL...which made me wonder why the original author bothered to use Hibernate. I thought it was supposed to make the bad SQL all go away.... > > 2) Make sure your connection properties were set properly? > It was running with a NATIVE driver with direct access to the database...no network latency here. > > 3) Enable lazy loading as necessary to reduce database joins and calls? > It was using lazy loading. > > 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. I cannot use caching because the database is shared by multiple systems (see criteria #2). > > Regards, > David, a happy hibernate user After all that, I have to ask: Why should I bother? I tried it, I really did. In fact, I tried it several times. Each time, I got a little further before deciding there was too much pain involved to make it "easier" for me. So I switched to iBATIS and have not looked back, except when I was looking for another bottleneck to eliminate. Larry, a happy (and reasonably disagreeable) iBATIS user --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
