When Auto Commit is OFF the Statement Execution History wont work. release701
authorSubhashini Sooriarachchi <subslk@netbeans.org>
Thu, 03 Nov 2011 13:58:48 +0530
branchrelease701
changeset 5507aedf781db5
parent 54 4bc8bbd37081
child 56 d6b7bb68d3e2
When Auto Commit is OFF the Statement Execution History wont work.
PLSQL/FileType/src/org/netbeans/modules/plsql/filetype/PlsqlDataObject.java
     1.1 --- a/PLSQL/FileType/src/org/netbeans/modules/plsql/filetype/PlsqlDataObject.java	Tue Nov 01 15:51:12 2011 +0100
     1.2 +++ b/PLSQL/FileType/src/org/netbeans/modules/plsql/filetype/PlsqlDataObject.java	Thu Nov 03 13:58:48 2011 +0530
     1.3 @@ -77,12 +77,14 @@
     1.4     private boolean isAnnotationsEnabled = false;
     1.5     private final PlsqlEditorSupport editorSupport;
     1.6     private DatabaseConnection databaseConnection;
     1.7 +   private StatementExecutionHistory statementExecutionHistory;
     1.8  
     1.9     public PlsqlDataObject(final FileObject fileObject, final PlsqlDataLoader loader) throws DataObjectExistsException, IOException {
    1.10        super(fileObject, loader);
    1.11        if (fileObject == null) {
    1.12           throw new IllegalArgumentException("FileObject cannot be null");
    1.13        }
    1.14 +      statementExecutionHistory = new StatementExecutionHistory();
    1.15        editorSupport = new PlsqlEditorSupport(this);
    1.16        getCookieSet().add(editorSupport);
    1.17        blockFactory = new PlsqlBlockFactory();
    1.18 @@ -165,7 +167,7 @@
    1.19     private void createLookup() {
    1.20        List<Object> objects = new ArrayList<Object>();
    1.21        objects.add(blockFactory);
    1.22 -      objects.add(new StatementExecutionHistory());
    1.23 +      objects.add(statementExecutionHistory);
    1.24        
    1.25         if (annotationManager != null) {
    1.26             objects.add(annotationManager);