dependabot[bot] opened a new pull request, #45706: URL: https://github.com/apache/superset/pull/45706
Bumps [syntaqlite](https://github.com/LalitMaganti/syntaqlite) from 0.12.1 to 0.13.0. <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.13.0</h2> <p><strong>Breaking change: aligning how tables and views are represented across languages</strong></p> <p>Tables and views are described the same way in Rust, C, JSON and RPC. A missing or <code>null</code> column list means the columns are unknown, and an empty list means there are none.</p> <table> <thead> <tr> <th>Before</th> <th>After</th> </tr> </thead> <tbody> <tr> <td>Rust <code>insert_table(name, Some(cols), false)</code></td> <td><code>insert_table(TableDef::new(name).columns(cols))</code></td> </tr> <tr> <td>Rust <code>insert_table(name, None, false)</code></td> <td><code>insert_table(TableDef::new(name))</code></td> </tr> <tr> <td>Rust <code>insert_table(name, cols, true)</code></td> <td><code>insert_table(TableDef::new(name).columns(cols).without_rowid())</code></td> </tr> <tr> <td>Rust <code>insert_view(name, Some(cols))</code></td> <td><code>insert_view(ViewDef::new(name).columns(cols))</code></td> </tr> <tr> <td>C <code>SyntaqliteRelationDef</code></td> <td><code>SyntaqliteViewDef</code></td> </tr> <tr> <td>JSON <code>"columns": []</code> for unknown columns</td> <td>Omit <code>columns</code> or pass <code>null</code></td> </tr> </tbody> </table> <p><strong>Analyzer</strong></p> <ul> <li>Catches many more errors that SQLite reports, such as wrong column or value counts in compound SELECTs, INSERTs, VALUES and subqueries, misused row values, undefined windows, and changes to views or built-in tables. Each has its own check, on by default.</li> <li>Checks DDL against the tables it touches: indexes, constraints, generated columns and triggers, with dropped tables no longer treated as existing.</li> <li>Schemas can declare generated and hidden columns, and <code>SELECT *</code> expands the same way SQLite does.</li> </ul> <p><strong>Language server</strong></p> <ul> <li>Completion suggests only names that fit at the cursor, from the tables in the query, ranked by what you have typed.</li> <li>Go-to-definition, find references and rename cover much more of the schema, including schema files set in <code>syntaqlite.toml</code>.</li> <li>Fixed schemas not loading when <code>--config</code> is a relative path.</li> </ul> <p><strong>Formatter</strong></p> <ul> <li>A comment before a statement no longer changes how its <code>VALUES</code> rows wrap.</li> </ul> </blockquote> </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.13.0</h2> <p><strong>Breaking: one schema shape everywhere</strong></p> <p>Tables and views are described the same way in Rust, C, JSON and RPC. A missing or <code>null</code> column list means the columns are unknown, and an empty list means there are none.</p> <table> <thead> <tr> <th>Before</th> <th>After</th> </tr> </thead> <tbody> <tr> <td>Rust <code>insert_table(name, Some(cols), false)</code></td> <td><code>insert_table(TableDef::new(name).columns(cols))</code></td> </tr> <tr> <td>Rust <code>insert_table(name, None, false)</code></td> <td><code>insert_table(TableDef::new(name))</code></td> </tr> <tr> <td>Rust <code>insert_table(name, cols, true)</code></td> <td><code>insert_table(TableDef::new(name).columns(cols).without_rowid())</code></td> </tr> <tr> <td>Rust <code>insert_view(name, Some(cols))</code></td> <td><code>insert_view(ViewDef::new(name).columns(cols))</code></td> </tr> <tr> <td>C <code>SyntaqliteRelationDef</code></td> <td><code>SyntaqliteViewDef</code></td> </tr> <tr> <td>JSON <code>"columns": []</code> for unknown columns</td> <td>Omit <code>columns</code> or pass <code>null</code></td> </tr> </tbody> </table> <p><strong>Analyzer</strong></p> <ul> <li>Catches many more errors that SQLite reports, such as wrong column or value counts in compound SELECTs, INSERTs, VALUES and subqueries, misused row values, undefined windows, and changes to views or built-in tables. Each has its own check, on by default.</li> <li>Checks DDL against the tables it touches: indexes, constraints, generated columns and triggers, with dropped tables no longer treated as existing.</li> <li>Schemas can declare generated and hidden columns, and <code>SELECT *</code> expands the same way SQLite does.</li> </ul> <p><strong>Language server</strong></p> <ul> <li>Completion suggests only names that fit at the cursor, from the tables in the query, ranked by what you have typed.</li> <li>Go-to-definition, find references and rename cover much more of the schema, including schema files set in <code>syntaqlite.toml</code>.</li> <li>Fixed schemas not loading when <code>--config</code> is a relative path.</li> </ul> <p><strong>Formatter</strong></p> <ul> <li>A comment before a statement no longer changes how its <code>VALUES</code> rows wrap.</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/LalitMaganti/syntaqlite/commit/da6cf78a0217ed5f8e1c3050850051370308cd91";><code>da6cf78</code></a> synq: bump version to 0.13.0 (<a href="https://redirect.github.com/LalitMaganti/syntaqlite/issues/473";>#473</a>)</li> <li><a href="https://github.com/LalitMaganti/syntaqlite/commit/ddce4a127f54f9ab601f9e450692fcd6abe830d2";><code>ddce4a1</code></a> synq: write changelogs grouped by theme, without PR links (<a href="https://redirect.github.com/LalitMaganti/syntaqlite/issues/474";>#474</a>)</li> <li><a href="https://github.com/LalitMaganti/syntaqlite/commit/97e030c1ff053d07563bd354a9d6747a7de71591";><code>97e030c</code></a> synq: accept nested row values only in WHERE and ON terms (<a href="https://redirect.github.com/LalitMaganti/syntaqlite/issues/472";>#472</a>)</li> <li><a href="https://github.com/LalitMaganti/syntaqlite/commit/6827537c66f76cb400daa14dd52a21f9644e6e21";><code>6827537</code></a> synq: flag misused row values (<a href="https://redirect.github.com/LalitMaganti/syntaqlite/issues/471";>#471</a>)</li> <li><a href="https://github.com/LalitMaganti/syntaqlite/commit/12fcae8d7df14913235c0b1f37453bdb89aba9ad";><code>12fcae8</code></a> synq: split the semantic walker into a module (<a href="https://redirect.github.com/LalitMaganti/syntaqlite/issues/469";>#469</a>)</li> <li><a href="https://github.com/LalitMaganti/syntaqlite/commit/aa6c9f4562f48d7f4b056954fc8b7dd59d6722d3";><code>aa6c9f4</code></a> synq: flag subqueries returning the wrong number of columns (<a href="https://redirect.github.com/LalitMaganti/syntaqlite/issues/468";>#468</a>)</li> <li><a href="https://github.com/LalitMaganti/syntaqlite/commit/e3c11bbeaead1a1b8496027c069a6db120b75e29";><code>e3c11bb</code></a> synq: flag INSERTs whose values don't fill the target's columns (<a href="https://redirect.github.com/LalitMaganti/syntaqlite/issues/461";>#461</a>)</li> <li><a href="https://github.com/LalitMaganti/syntaqlite/commit/f3f6ba3398d44d65dda49cef1d975481b8c374ee";><code>f3f6ba3</code></a> synq: share the map boilerplate in diagnostic serialization (<a href="https://redirect.github.com/LalitMaganti/syntaqlite/issues/467";>#467</a>)</li> <li><a href="https://github.com/LalitMaganti/syntaqlite/commit/23979ba802696da5459b73927f4d286fe9677434";><code>23979ba</code></a> synq: expand SELECT * the way SQLite does, everywhere (<a href="https://redirect.github.com/LalitMaganti/syntaqlite/issues/466";>#466</a>)</li> <li><a href="https://github.com/LalitMaganti/syntaqlite/commit/3738340a884755f7e5bcb698d2119566ec744d76";><code>3738340</code></a> synq: flag VALUES rows with different numbers of terms (<a href="https://redirect.github.com/LalitMaganti/syntaqlite/issues/463";>#463</a>)</li> <li>Additional commits viewable in <a href="https://github.com/LalitMaganti/syntaqlite/compare/v0.12.1...v0.13.0";>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]
