Drop the DEBUG log — redundant with sqlalchemy.engine's own logging

The prior commit added a DEBUG log in __init__ recording the compiled
statement. SQLAlchemy's own sqlalchemy.engine logger already exposes
the compiled SQL (via echo=True or the standard engine logger), so
our log duplicates that surface for no added signal. Dropping it
keeps the dialect consistent with the existing "warnings only" logging
style — no other DEBUG-level log exists in the codebase.

Co-authored-by: Isaac
Signed-off-by: Madhavendra Rathore <madhavendra.rathore@databricks.com>

Author: msrathore-db

src/databricks/sqlalchemy/_ddl.py

@@ -120,18 +120,6 @@ class DatabricksStatementCompiler(compiler.SQLCompiler):
     bindtemplate = property(lambda self: self._BIND_TEMPLATE, lambda self, _: None)
     compilation_bindtemplate = property(lambda self: self._BIND_TEMPLATE, lambda self, _: None)
 
-    def __init__(self, *args, **kwargs):
-        super().__init__(*args, **kwargs)
-        # One-line trace of what we rendered — helps debug reported SQL
-        # issues without adding per-bindparam noise.
-        if logger.isEnabledFor(logging.DEBUG):
-            logger.debug(
-                "DatabricksStatementCompiler compiled statement with "
-                "backtick-quoted bind markers (template=%s): %s",
-                self._BIND_TEMPLATE,
-                self.string,
-            )
-
     def limit_clause(self, select, **kw):
         """Identical to the default implementation of SQLCompiler.limit_clause except it writes LIMIT ALL instead of LIMIT -1,
         since Databricks SQL doesn't support the latter.