dependabot[bot] opened a new pull request, #45320: URL: https://github.com/apache/superset/pull/45320
Bumps [syntaqlite](https://github.com/LalitMaganti/syntaqlite) from 0.9.0 to 0.12.1. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/LalitMaganti/syntaqlite/releases";>syntaqlite's releases</a>.</em></p> <blockquote> <h2>v0.12.1</h2> <p><strong>Custom dialects:</strong></p> <ul> <li>A node expander can read the result of the statement it is expanding, such as its root. (<a href="https://redirect.github.com/LalitMaganti/syntaqlite/pull/406";>#406</a>).</li> </ul> <h2>v0.12.0</h2> <p><strong>Custom dialects:</strong></p> <ul> <li>Nodes marked for expansion are now expanded once their statement is parsed, not while it is still being parsed, so the host can see the whole statement, such as the CTEs a node reads. A node that can't be placed fails its statement instead of being silently skipped (<a href="https://redirect.github.com/LalitMaganti/syntaqlite/pull/404";>#404</a>).</li> <li>Generating a dialect gives the same keyword tables on every run (<a href="https://redirect.github.com/LalitMaganti/syntaqlite/pull/403";>#403</a>).</li> </ul> <h2>v0.11.2</h2> <p><strong>Parser:</strong></p> <ul> <li>Fix <code>syntaqlite_parser_node_site</code> for statements that start with <code>EXPLAIN</code>. It ignored the <code>EXPLAIN</code> keyword when working out where a statement was written, so for <code>EXPLAIN QUERY PLAN my_macro!()</code> it said the statement was inside the macro's expansion rather than in the text you wrote (<a href="https://redirect.github.com/LalitMaganti/syntaqlite/pull/400";>#400</a>).</li> </ul> <h2>v0.11.1</h2> <blockquote> <p>Note: The 0.11.0 GitHub release was never published (its macOS and Windows builds failed).</p> </blockquote> <h3>0.11.1</h3> <p><strong>C library:</strong></p> <ul> <li>Fix the macOS and Windows release builds, which failed to link because the exported symbol list still used the names removed in 0.11.0. The C library now also exports the node expansion functions (<a href="https://redirect.github.com/LalitMaganti/syntaqlite/pull/397";>#397</a>).</li> </ul> <h3>0.11.0</h3> <p><strong>Breaking: macro rewrites renamed to rewrites</strong> (<a href="https://redirect.github.com/LalitMaganti/syntaqlite/pull/395";>#395</a>):</p> <table> <thead> <tr> <th>Before</th> <th>After</th> </tr> </thead> <tbody> <tr> <td><code>SyntaqliteMacroRewrite</code></td> <td><code>SyntaqliteRewrite</code></td> </tr> <tr> <td><code>syntaqlite_result_macro_count</code></td> <td><code>syntaqlite_result_rewrite_count</code></td> </tr> <tr> <td><code>syntaqlite_result_macro_rewrite_at</code></td> <td><code>syntaqlite_result_rewrite_at</code></td> </tr> <tr> <td><code>SYNTAQLITE_MACRO_PARENT_SOURCE</code></td> <td><code>SYNTAQLITE_REWRITE_PARENT_SOURCE</code></td> </tr> <tr> <td>Rust <code>MacroRewrite</code></td> <td><code>Rewrite</code></td> </tr> <tr> <td>Rust <code>macro_rewrites()</code></td> <td><code>rewrites()</code></td> </tr> </tbody> </table> <p><strong>Custom dialects:</strong></p> <ul> <li>Dialects can now have the host replace a parsed node with its own SQL. Call <code>synq_parser_expand_node</code> from a grammar action and set a callback with <code>syntaqlite_parser_set_node_expander</code>. The replacement shows up as a rewrite, and <code>Rewrite::kind()</code> tells node expansions apart from macro calls (<a href="https://redirect.github.com/LalitMaganti/syntaqlite/pull/394";>#394</a>).</li> </ul> <h2>v0.10.2</h2> <p><strong>Custom dialects:</strong></p> <ul> <li>Add fixed operator tokens such as <code>|></code> using separate <code>.tokens</code> files and the repeatable <code>--tokens-file</code> option. Tokens are available to <code>.y</code> grammar rules without becoming SQL keywords (<a href="https://redirect.github.com/LalitMaganti/syntaqlite/pull/392";>#392</a>).</li> </ul> <h2>v0.10.1</h2> <p><strong>Formatter:</strong></p> <ul> <li>Macro calls that overflow the line width now break one argument per line with the closing paren at the opener's indent, instead of wrapping inside an argument's expression (<a href="https://redirect.github.com/LalitMaganti/syntaqlite/pull/390";>#390</a>).</li> <li><code>ORDER BY</code> and <code>LIMIT</code> on a compound <code>SELECT</code> now move to their own lines when the last arm spans multiple lines, instead of trailing the arm's final clause (<a href="https://redirect.github.com/LalitMaganti/syntaqlite/pull/390";>#390</a>).</li> </ul> <h2>v0.10.0</h2> <p><strong>Performance:</strong></p> <ul> <li>Reduced formatting time by roughly 18–19% versus 0.9.0 across four benchmark inputs, from a single SELECT to 500-statement scripts, through token and comment cursor improvements, reused node-field buffers, and faster opcode dispatch (<a href="https://redirect.github.com/LalitMaganti/syntaqlite/pull/381";>#381</a>, <a href="https://redirect.github.com/LalitMaganti/syntaqlite/pull/384";>#384</a>, <a href="https://redirect.github.com/LalitMaganti/syntaqlite/pull/385";>#385</a>, <a href="https://redirect.github.com/LalitMaganti/syntaqlite/pull/388";>#388</a>).</li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/LalitMaganti/syntaqlite/blob/main/CHANGELOG.md";>syntaqlite's changelog</a>.</em></p> <blockquote> <h2>0.12.1</h2> <p><strong>Custom dialects:</strong></p> <ul> <li>A node expander can read the result of the statement it is expanding, such as its root. Before, the result still described the previous statement, and nothing for the first statement of a source (<a href="https://redirect.github.com/LalitMaganti/syntaqlite/pull/406";>#406</a>).</li> </ul> <h2>0.12.0</h2> <p><strong>Custom dialects:</strong></p> <ul> <li>Nodes marked for expansion are now expanded once their statement is parsed, not while it is still being parsed, so the host can see the whole statement, such as the CTEs a node reads. A node that can't be placed fails its statement instead of being silently skipped (<a href="https://redirect.github.com/LalitMaganti/syntaqlite/pull/404";>#404</a>).</li> <li>Generating a dialect gives the same keyword tables on every run (<a href="https://redirect.github.com/LalitMaganti/syntaqlite/pull/403";>#403</a>).</li> </ul> <h2>0.11.2</h2> <p><strong>Parser:</strong></p> <ul> <li>Fix <code>syntaqlite_parser_node_site</code> for statements that start with <code>EXPLAIN</code>. It ignored the <code>EXPLAIN</code> keyword when working out where a statement was written, so for <code>EXPLAIN QUERY PLAN my_macro!()</code> it said the statement was inside the macro's expansion rather than in the text you wrote (<a href="https://redirect.github.com/LalitMaganti/syntaqlite/pull/400";>#400</a>).</li> </ul> <h2>0.11.1</h2> <p><strong>C library:</strong></p> <ul> <li>Fix the macOS and Windows release builds, which failed to link because the exported symbol list still used the names removed in 0.11.0. The C library now also exports the node expansion functions (<a href="https://redirect.github.com/LalitMaganti/syntaqlite/pull/397";>#397</a>).</li> </ul> <h2>0.11.0</h2> <p><strong>Breaking: macro rewrites renamed to rewrites</strong> (<a href="https://redirect.github.com/LalitMaganti/syntaqlite/pull/395";>#395</a>):</p> <table> <thead> <tr> <th>Before</th> <th>After</th> </tr> </thead> <tbody> <tr> <td><code>SyntaqliteMacroRewrite</code></td> <td><code>SyntaqliteRewrite</code></td> </tr> <tr> <td><code>syntaqlite_result_macro_count</code></td> <td><code>syntaqlite_result_rewrite_count</code></td> </tr> <tr> <td><code>syntaqlite_result_macro_rewrite_at</code></td> <td><code>syntaqlite_result_rewrite_at</code></td> </tr> <tr> <td><code>SYNTAQLITE_MACRO_PARENT_SOURCE</code></td> <td><code>SYNTAQLITE_REWRITE_PARENT_SOURCE</code></td> </tr> <tr> <td>Rust <code>MacroRewrite</code></td> <td><code>Rewrite</code></td> </tr> <tr> <td>Rust <code>macro_rewrites()</code></td> <td><code>rewrites()</code></td> </tr> </tbody> </table> <p><strong>Custom dialects:</strong></p> <ul> <li>Dialects can now have the host replace a parsed node with its own SQL. Call <code>synq_parser_expand_node</code> from a grammar action and set a callback with <code>syntaqlite_parser_set_node_expander</code>. The replacement shows up as a rewrite, and <code>Rewrite::kind()</code> tells node expansions apart from macro calls (<a href="https://redirect.github.com/LalitMaganti/syntaqlite/pull/394";>#394</a>).</li> </ul> <h2>0.10.2</h2> <p><strong>Custom dialects:</strong></p> <ul> <li>Add fixed operator tokens such as <code>|></code> using separate <code>.tokens</code> files and the repeatable <code>--tokens-file</code> option. Tokens are available to <code>.y</code> grammar rules without becoming SQL keywords (<a href="https://redirect.github.com/LalitMaganti/syntaqlite/pull/392";>#392</a>).</li> </ul> <h2>0.10.1</h2> <p><strong>Formatter:</strong></p> <ul> <li>Macro calls that overflow the line width now break one argument per line with the closing paren at the opener's indent, instead of wrapping inside an argument's expression (<a href="https://redirect.github.com/LalitMaganti/syntaqlite/pull/390";>#390</a>).</li> <li><code>ORDER BY</code> and <code>LIMIT</code> on a compound <code>SELECT</code> now move to their own lines when the last arm spans multiple lines, instead of trailing the arm's final clause (<a href="https://redirect.github.com/LalitMaganti/syntaqlite/pull/390";>#390</a>).</li> </ul> <h2>0.10.0</h2> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/LalitMaganti/syntaqlite/commit/d15044994323ebefd364da4503f1eaaf6383133f";><code>d150449</code></a> synq: bump version to 0.12.1 (<a href="https://redirect.github.com/LalitMaganti/syntaqlite/issues/407";>#407</a>)</li> <li><a href="https://github.com/LalitMaganti/syntaqlite/commit/7fbace9d8acb9fca86a9b4a563b4bb9ae5999074";><code>7fbace9</code></a> synq: let the node expander read the statement's root (<a href="https://redirect.github.com/LalitMaganti/syntaqlite/issues/406";>#406</a>)</li> <li><a href="https://github.com/LalitMaganti/syntaqlite/commit/1453e21a8c6b8d91fe9345fe5dc422009cdcd8ab";><code>1453e21</code></a> synq: rebaseline the public API for the latest nightly rustdoc (<a href="https://redirect.github.com/LalitMaganti/syntaqlite/issues/408";>#408</a>)</li> <li><a href="https://github.com/LalitMaganti/syntaqlite/commit/dd2f500d9db2a8e7c60e5f95b50226cf64fc0090";><code>dd2f500</code></a> synq: bump version to 0.12.0 (<a href="https://redirect.github.com/LalitMaganti/syntaqlite/issues/405";>#405</a>)</li> <li><a href="https://github.com/LalitMaganti/syntaqlite/commit/fd69dda692410de4ae37ee512d059dab0dec54a9";><code>fd69dda</code></a> synq: expand nodes once their statement is parsed (<a href="https://redirect.github.com/LalitMaganti/syntaqlite/issues/404";>#404</a>)</li> <li><a href="https://github.com/LalitMaganti/syntaqlite/commit/c6f2b4b9521033345a14271b96a44af45d7ede63";><code>c6f2b4b</code></a> synq: generate the same keyword table on every run (<a href="https://redirect.github.com/LalitMaganti/syntaqlite/issues/403";>#403</a>)</li> <li><a href="https://github.com/LalitMaganti/syntaqlite/commit/70e15faf223d997039d4eab8cc26fc71984d1f5a";><code>70e15fa</code></a> synq: explain the 0.11.2 changelog entry plainly (<a href="https://redirect.github.com/LalitMaganti/syntaqlite/issues/402";>#402</a>)</li> <li><a href="https://github.com/LalitMaganti/syntaqlite/commit/6083f690047c5882bd5e27fe1c81d35a18e50257";><code>6083f69</code></a> synq: bump version to 0.11.2 (<a href="https://redirect.github.com/LalitMaganti/syntaqlite/issues/401";>#401</a>)</li> <li><a href="https://github.com/LalitMaganti/syntaqlite/commit/d16e45c78f54ecc60806eeb2129bac4fb2573e5c";><code>d16e45c</code></a> synq: place explained statements where EXPLAIN is written (<a href="https://redirect.github.com/LalitMaganti/syntaqlite/issues/400";>#400</a>)</li> <li><a href="https://github.com/LalitMaganti/syntaqlite/commit/7866e52d26dc349d02053258b9f5c516e91fed7f";><code>7866e52</code></a> synq: check the C library exports what the headers declare (<a href="https://redirect.github.com/LalitMaganti/syntaqlite/issues/399";>#399</a>)</li> <li>Additional commits viewable in <a href="https://github.com/LalitMaganti/syntaqlite/compare/v0.9.0...v0.12.1";>compare view</a></li> </ul> </details> <br /> [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
