Community
Participate
Working Groups
Could you please check method SQLParserManager.setPostParseProcessors I guess the condition should be if ((postParseProcessors == null) || (postParseProcessors.size() == 0) ) { postParseProcessors = getInternalDefaultPostParseProcessorList(); } I can set the postParseProcessors to an empty list and this will skip default post parsing... // we always want to post parse process, at least the basic stuff! so // postParseProcessors == null really means // postParseProcessors == getInternalDefaultPostParseProcessorList() // but we want to hide that from the public if (postParseProcessors == null) { postParseProcessors = getInternalDefaultPostParseProcessorList(); } plugins/ org.eclipse.datatools.sqltools.parsers.sql_0.9.0.200605101/sqlparser.jar package org.eclipse.datatools.sqltools.parsers.sql; public abstract class SQLParserManager { /** * Sets the post parse processors used for semantical checks and resolvings * after successful syntactical parsing. * * @param postParseProcessors */ // ******** public final void setPostParseProcessors(List postParseProcessors) { // we always want to post parse process, at least the basic stuff! so // postParseProcessors == null really means // postParseProcessors == getInternalDefaultPostParseProcessorList() // but we want to hide that from the public if (postParseProcessors == null) { postParseProcessors = getInternalDefaultPostParseProcessorList(); } this.postParseProcessors = postParseProcessors; } // ******** }
Reassigned to Brian.
Created attachment 85697 [details] Patch for o.e.d.sqltools.parsers.sql plugin
Applied suggested change to SQLParserManager class in the 1.6M5 code stream. Set the plugin version to 1.0.0.200712201.
Closing...