Hello,

I have read the majority of the chapters of Hibernate in Action (not saying that I am an expert) and I came across a potential problem in my organization.

Like many large organizations we have a number of developers who are not as "Senior" as they would like you to believe. But many in the organization are - I am trying to setup a common approach to the database problem domain that will force developers into using PreparedStatements against our DB2 database. This is really now being mandated by our DBA group - it has to do with keeping their cache clean (not sure what that means on a DBA level).

I have read in the Preface of the Hib. in Action book that "people who had much more time to investigate performance optimizations that you have...Did you know for instance, that pooling PreparedStatements instances results in a significant performance increase?"

Can I take this to mean that if I was to build an application utilizing Hibernate 2.x or 3.x for that matter with:

hibernate.dialect=net.sf.hibernate.dialect.DB2400Dialect

We would be totally using PreparedStatements in within Hibernate and also would afford all the same features?

I have developed around Hibernate for about a year now (have formal training coming up in NYC) -- but I have on developed against MySQL (not that this would matter:-)

Any explanation would be greatly appreciated....

Starring