I noticed, that when you click on subpartitioned table, sqlnav freezes for few minutes. After clicking table you are executing three selects (nav.log), which are fast, but sqlnav waits for something, you must check.
Create table from attachement, and then cclick on it, watch what happend.
I attached my test, i clicked on three tables , when the last one is subpartitioned (watch clip from attachement), and then watch execution times in my nav.log.
Do you must execute enything trigered by selecting table? Sometimes users simply runs via objects using arrows… I remember, in sqlnav 5.0 clicking on objects was very slow, sqlnav was executing some sqls on each selected object.
All files are in zip file.
clip0018.zip (65.9 KB)