Hi, I realized that the cache paramter that I can specify when I open a jdbc connection works very well. The first time execution of a perpareStatement() takes very long, but additional calls use the cached version. I have many queries that contain something like this ... where id in ( 1, 2, 3, 4, 5, 6 ) ... Until now, I compose this query from java which might lead to problems with this caching because the parameter count changes and so the query might not be found in the cache. Would it help to change it to ... where id in ( ? ) and then call PreparedStatement.setArray(1, integerArray) ? bye
Daniel -- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
