On Thu, Mar 13, 2008 at 12:31 PM, David Fisher <[EMAIL PROTECTED]> wrote: > BTW - I had jumped in on the thread to explain how indexes can help > you deal with such horrible queries. Users can't always wait for the > developers. > > I am using 4.0 final and I inspected the dbscripts for the original > poster's mysql. I then noted what was present and confirmed what was > missing. > > > So in this case I would prefer to see us work to fix the query > > rather than just try and throw new indexes at the problem. > > Absolutely - unless it is too large a task. Either way it is probably > a JIRA issue for Roller. > > Maybe in the switch from Hibernate to JPA some setting was missed? > Maybe the 4.0 object model is more complicated that the poster's > prior 1.1?
The 4.0 data model is different from 1.1, less complex in some ways (category & bookmark hierarchy) and more complex in others (group blogs). > Perhaps Dave can explain the reasons why the query is so complex. I > suspect it has to with creating a Velocity model in a single query? The SQL generation is done by the ORM, which used to be Hibernate and is now OpenJPA. I hope upgrading from OpenJPA 0.9.7 to 1.1 will address some of these problems, if not then we should make sure that Roller can be used with Hibernate/JPA,TopLink Essentials/JPA and/or EclipseLink/JPA. - Dave
