From: Pjm <pj...@sa...> - 2003-10-01 17:28:04
|
Adrian Roy Tivey wrote: >>Arnaud- >> >>Jonathan has handed responsibility for the WDK over to me and Angel, >>since he has moved to D.C. >> >>I'll look into it. Feel free to delve into the code and find out >>whatever you can. >> >>Steve > > > Does anybody know how reliable Statement.setQueryTimeout is on Oracle? If it's > robust we could easily switch to that. Then we get the timeout report in (more > or less) the right bit of the code to handle it. The statement timeout code works fine. Its more the fact that if one of the sub queries fails (for whatever reason) then the cacheXXXX table does not get created. Thus the query that intersects with it will also fail. The code does not handle this and the results page has a table with no rows. The next time that query runs it will look for the cacheXXXX table and fail. The user will think the query found nothing. Paul. |