This will be a bit tricky to reproduce... :-)1. Add the attached file to the Eclipse workspace and open it2. In the file, connect to your database and create the view (execute button)3. Check in the file to SVN4. Change the view (e.g. SELECT 3 VAL FROM DUAL) and execute it5. Check in the change to SVN6. Open the first revision of the view through the History (see screenshot)7. Execute the view from the History -> NullPointerExceptionSince the stacktrace is four methods inside of TEE, I doubt that it's a SVN problem:!ENTRY com.quest.toadext.ui 4 2 2011-12-15 14:10:30.494!MESSAGE Problems occurred when invoking code from plug-in: "com.quest.toadext.ui".!STACK 0java.lang.NullPointerException at com.quest.toadext.project.util.MarkerManager.clearCompileAnnotations(Unknown Source) at com.quest.toadext.plsqlviewer.PlSqlSourceViewer.clearCompileErrors(Unknown Source) at com.quest.toadext.editors.plsql.PlSqlEditor$SaveAndCompileAction.execute(Unknown Source) at com.quest.toadext.ui.actions.ToadextAction$1.run(Unknown Source) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:49) at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:175) at com.quest.toadext.ui.actions.ToadextAction.run(Unknown Source)
Thanks for your reply, Tomas.Yes, being able to put view and package source code in version control is a very nice feature of TEE as opposed to the full-fledged Toad, as everything is well integrated in Eclipse. That would also allow me to use CVS or Git or any other version control system with Eclipse plugins.I rarely re-apply old versions of a view/package to the database, but every now and then, it comes in handy.CheersLukas
In future I will use my Sql Code also on SVN ...for now the problem is, that on my work I'm the only one who uses the SQL Code from file system so I can use SVN only for the projects on which I'm working alone.