Document the blank line separator option

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>

Author: edeadington

src/main/java/net/sf/jsqlparser/parser/SimpleCharStream.java

@@ -10,9 +10,10 @@
 /* Generated By:JavaCC: Do not edit this line by hand. SimpleCharStream.java Version 8.0.0 */
 /*
  * Warning: this file is maintained by hand on top of the JavaCC template. Among other manual
- * adjustments it carries the in-buffer '#' rewrite in BeginToken(), which
- * Feature.allowHashLineComments depends on. Never overwrite it with a freshly generated
- * SimpleCharStream, that would silently drop the rewrite and break allowHashLineComments.
+ * adjustments it carries the in-buffer '#' and blank line rewrites in BeginToken(), which
+ * Feature.allowHashLineComments and Feature.allowBlankLinesAsStatementSeparator depend on. Never
+ * overwrite it with a freshly generated SimpleCharStream, that would silently drop the rewrites and
+ * break both features.
  */
 package net.sf.jsqlparser.parser;
 

src/main/java/net/sf/jsqlparser/parser/feature/Feature.java

@@ -890,9 +890,9 @@ public enum Feature {
     allowHashLineComments(false),
 
     /**
-     * treats three consecutive newlines as a statement separator, like `;`; enabled by default.
-     * When disabled, blank lines are plain whitespace, so a statement containing them is parsed
-     * whole instead of being cut off at the first run of blank lines
+     * treats three consecutive newlines as a statement separator (enabled by default). When
+     * disabled, blank lines are plain whitespace, so a statement containing them is parsed whole
+     * instead of being cut off at the first run of blank lines
      */
     allowBlankLinesAsStatementSeparator(true),
 

src/site/sphinx/usage.rst

@@ -204,6 +204,7 @@ For several statements at once, use ``CCJSqlParserUtil.parseStatements()``, whic
 .. note::
 
     Supported statement separators are semicolon ``;``, ``GO``, slash ``/`` and two empty lines ``\n\n\n``.
+    Use ``withBlankLinesAsSeparator(false)`` to treat empty lines as plain whitespace instead.
 
 If parsing fails on syntax JSQLParser does not know, see :ref:`Handle Parse Errors` — and please `open an issue <https://github.com/JSQLParser/JSqlParser/issues>`_, missing syntax gets added on demand.
 
@@ -1571,6 +1572,8 @@ The individual features
       - ``".."`` reads as a string literal instead of a quoted identifier (BigQuery, Spark/Databricks, MySQL default ``sql_mode``)
     * - ``withHashLineComments``
       - ``#`` starts a line comment
+    * - ``withBlankLinesAsSeparator``
+      - ``false`` stops two empty lines (``\n\n\n``) ending a statement, so they read as plain whitespace
     * - ``withAdjacentStringLiterals``
       - adjacent string literals concatenate: ``NEWLINE`` (SQL standard, PostgreSQL) or ``WHITESPACE`` (GoogleSQL, Spark/Databricks); ``true`` selects ``NEWLINE``, ``false`` switches it off
     * - ``withAllowComplexParsing``