Searching for an existing calendar to add is slow and appears to execute many SQL statements when SQL Logging is enabled, potentially causing the request to time out.

Steps to Reproduce

1. Set up Confluence and Team Calendars, with many users and calendars (use existing test data if required)
2. Enable detailed SQL logging
3. Log in to Confluence and go to Calendars
4. Click to Add Calendar
5. Select Existing Calendar
6. Enter part of the name of an existing calendar
7. Tail the confluence log - you will see many lines like this:

   2014-01-28 00:47:05,045 TRACE [http-10523-13] [sf.hibernate.type.StringType] nullSafeGet returning 'fc72b896-a4d1-44ff-b164-7715a9f2e3e9' as column: x0_0_
   

8. After 2 minutes, the front end will time out and say "No results found for .."
9. Keep watching the logs. After around 6 minutes total on my instance, the logging stopped.

NB: Without detailed SQL logging enabled these requests complete and calendars can be found and added, however I'm concerned this is simply highlighting a larger performance issue that should be investigated. If there is a performance issue, any environmental latency could cause the above timeout, or just very slow calendar retrieval.