1 of 1 people found this helpful
For that you should look into DTP which is a much more complete Database browser.
If you already have the Hibernate Configuration view open to see all the Class objects available, and the HQL editor open (the HQL/JPA-QL query you want to optimize), and have the Dynamic SQL Preview view open to see the actual query, I was kind of hoping to just add to the Hibernate Configuration view (that you may already have open) that index information in its Database tree node.
Just seems like keep adding in more views/swapping to more tools (such as a DTP view), when there is an opportunity for improvement.
Yes, but we don't read *all* metadata I think you want to get at - DTP does.
For now, using the DTP View will give your more info.
In case of you using DTP connections we could probably put in a "DTP Database" node instead of/or next our "Database" node which
is just whatever the Hibernate Configuration model contains about the database and not what is necessarily directly in there.
Having a DTP Database node option/instead of current database node in hibernate tools actually would be great, with the one expectation of it being a more convenient starting point in the DTP tree (instead the deep-tree digging one must normally do with DTP server->database->schema-><actual stuff I care about> (maybe to schema then stuff, as some people work with multiple schemas).
jira feauture request is your friend
patches implementing it your best friend