DbVisualizer 5.0.0.8 is now available

Exception in thread "AWT-EventQueue-1" java.lang.NullPointerException at com.onseven.dbvis.Z.G.D$3.actionPerformed(Unknown Source) at javax.swing.AbstractButton.fireActionPerformed(Unknown Source) at javax.swing.AbstractButton$Handler.actionPerformed(Unknown Source) at javax.swing.DefaultButtonModel.fireActionPerformed(Unknown Source) at javax.swing.DefaultButtonModel.setPressed(Unknown Source) at javax.swing.plaf.basic.BasicButtonListener.mouseReleased(Unknown Source) at java.awt.Component.processMouseEvent(Unknown Source) at javax.swing.JComponent.processMouseEvent(Unknown Source) at java.awt.Component.processEvent(Unknown Source) at java.awt.Container.processEvent(Unknown Source) at java.awt.Component.dispatchEventImpl(Unknown Source) at java.awt.Container.dispatchEventImpl(Unknown Source) at java.awt.Component.dispatchEvent(Unknown Source) at java.awt.LightweightDispatcher.retargetMouseEvent(Unknown Source) at java.awt.LightweightDispatcher.processMouseEvent(Unknown Source) at java.awt.LightweightDispatcher.dispatchEvent(Unknown Source) at java.awt.Container.dispatchEventImpl(Unknown Source) at java.awt.Window.dispatchEventImpl(Unknown Source) at java.awt.Component.dispatchEvent(Unknown Source) at java.awt.EventQueue.dispatchEvent(Unknown Source) at com.onseven.dbvis.H.A.d.dispatchEvent(Unknown Source) at java.awt.EventDispatchThread.pumpOneEventForHierarchy(Unknown Source) at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source) at java.awt.EventDispatchThread.pumpEvents(Unknown Source) at java.awt.EventDispatchThread.pumpEvents(Unknown Source) at java.awt.EventDispatchThread.run(Unknown Source) I re-created a package specification and hit compile trigger in the schema tree for that schema. regards, Ronald.

Hi Roger, it does not happen all the time and I am not 100% sure what action actually is the trigger. The object - in this case a trigger - takes a while to compile. The dialogbox is still showing while the compile is running and I was not sure if I it [execute] so I hit it again. At that point the NPE popped up. It could very well be that the second click on [execute] causes the NPE. Maybe it's an idea to disable the execute button when the execute already has been clicked on and make that visible. Ronald.

DDL tab on tables is not working. I need the task manager to end the dbvis process. Reproduced when connected as dba and as sysdba. select a table from the schema tree and hit the DDL tab. Ronald.

Hi Roger, 1) when can we expect triggers as child of the table in the schema tree? 2) a while ago we discussed the possibility to have more options on output grids for selects coming from the schema tree. One very nice option would be to have a graph as output (for scheduler runtime behaviour for example). Is this already possible? The normal grid from the sqlcommander has (almost) all I want. thanks, Ronald.

Hmm. problem with this is that I have to kill dbvis. How can I have the debug info directly written to a logfile? Just did it again: connect using the default oracle profile as a dba to a 9207 database. Find a schema that has tables Find open the tables leaf select the second table hit the DDL tab and bang; no reponse at all. Cpu on database server nor the client pc is doing a lot.

I hope you find something usefull in here Roger. Currently I am on windoze :-( Ronald.

Hi Roger, I still think you should only show schema in the objects tree and not all users. In a little database this qry will be good enough: select username TABLE_SCHEM from ${#cp.SystemTablePrefix}_users where exists (select 'x' from sys.obj$ where user_id = owner# and type# != 5) union select 'PUBLIC' from dual In a database with thousands of users this takes 3 seconds and makes the schema browser usable. I hope it will do for most of us. The select username from dba_users takes half of the time but costs more than double the time when browsing. Ronald.