Logging Long Running Queries
When creating an application with many queries and a great deal of data, it is common practice to do development with a subset of the data.
While this makes it faster to develop, it makes it harder to know what queries are slow or poorly optimized.
It would be very helpful for developers and DBAs to provide a way for iBATIS to log long running queries in a way that makes them stand out as potential bottlenecks.
This change would likely include a change to the sqlmap config file (for a default threshold value) and a new attribute for mapped statements (for overriding that default).