diff options
| author | Daniel Baumann <daniel.baumann@progress-linux.org> | 2024-05-05 11:14:27 +0000 |
|---|---|---|
| committer | Daniel Baumann <daniel.baumann@progress-linux.org> | 2024-05-05 11:14:27 +0000 |
| commit | 86c29b46f4c7494401cc2ee272d0dec2b8256eff (patch) | |
| tree | 7a9ad6cc3c1bad2259ad3133e22a55a2179558a5 /docs/sqlglot.html | |
| parent | Adding upstream version 23.13.1. (diff) | |
| download | sqlglot-86c29b46f4c7494401cc2ee272d0dec2b8256eff.tar.xz sqlglot-86c29b46f4c7494401cc2ee272d0dec2b8256eff.zip | |
Adding upstream version 23.13.7.upstream/23.13.7
Signed-off-by: Daniel Baumann <daniel.baumann@progress-linux.org>
Diffstat (limited to 'docs/sqlglot.html')
| -rw-r--r-- | docs/sqlglot.html | 6 |
1 files changed, 5 insertions, 1 deletions
diff --git a/docs/sqlglot.html b/docs/sqlglot.html index 2442e43..ce92b08 100644 --- a/docs/sqlglot.html +++ b/docs/sqlglot.html @@ -361,7 +361,7 @@ <h3 id="unsupported-errors">Unsupported Errors</h3> -<p>It may not be possible to translate some queries between certain dialects. For these cases, SQLGlot may emit a warning and proceeds to do a best-effort translation by default. Transpilation is difficult and not all permutations are supported. If transpilation does not work, it may not be implemented yet. Well documented / tested PRs / issues are appreciated. Some transpilation cases that require db schemas are made possible through the optimizer but are not included in base transpilation:</p> +<p>It may not be possible to translate some queries between certain dialects. For these cases, SQLGlot may emit a warning and will proceed to do a best-effort translation by default:</p> <div class="pdoc-code codehilite"> <pre><span></span><code><span class="kn">import</span> <span class="nn">sqlglot</span> @@ -386,6 +386,10 @@ <pre><code><a href="sqlglot/errors.html#UnsupportedError">sqlglot.errors.UnsupportedError</a>: APPROX_COUNT_DISTINCT does not support accuracy </code></pre> +<p>There are queries that require additional information to be accurately transpiled, such as the schemas of the tables referenced in them. This is because certain transformations are type-sensitive, meaning that type inference is needed in order to understand their semantics. Even though the <code>qualify</code> and <code>annotate_types</code> optimizer <a href="https://github.com/tobymao/sqlglot/tree/main/sqlglot/optimizer">rules</a> can help with this, they are not used by default because they add significant overhead and complexity.</p> + +<p>Transpilation is generally a hard problem, so SQLGlot employs an "incremental" approach to solving it. This means that there may be dialect pairs that currently lack support for some inputs, but this is expected to improve over time. We highly appreciate well-documented and tested issues or PRs, so feel free to <a href="#get-in-touch">reach out</a> if you need guidance!</p> + <h3 id="build-and-modify-sql">Build and Modify SQL</h3> <p>SQLGlot supports incrementally building SQL expressions:</p> |