It would be a very cool feature to have some sort of common errors detector in place and log warnings as issues are detected.
It should be optional of course and it would be turned off in production.
Specifically I though of this when reading this blog: http://management-platform.blogspot.com ... d-jpa.html

Here we have a very specific problem. query.setFirstResult(startRow), and query.setMaxResults(pageSize) are used which indicates the developer is probably implementing paging. But query contains no ORDER BY clause.

It's an easy to detect situation. It requires some kind of event model in place, and ErrorsDetectorListener (let's call it that) that collects info and matches it against a list of known 'situations'.

A feature like this could really help save a lot of headaches to many people.