dependabot[bot] opened a new pull request, #13884: URL: https://github.com/apache/datafusion/pull/13884
Updates the requirements on [sqllogictest](https://github.com/risinglightdb/sqllogictest-rs) to permit the latest version. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/risinglightdb/sqllogictest-rs/releases";>sqllogictest's releases</a>.</em></p> <blockquote> <h2>v0.24.0</h2> <h2>[0.24.0] - 2024-12-20</h2> <ul> <li>runner: Added a <code>Normalizer</code> type for normalizing result values. A new function <code>with_normalizer(normalizer: Normalizer)</code> has been added to the Runner to allow for specifying a custom Normalizer. The existing default normalizer is available via the <code>runner::default_normalizer(..)</code> function.</li> <li>parser: Added a new control mode <code>resultmode</code> that controls whether the results are in <code>valuewise</code> or <code>columnwise</code> mode. The default is <code>columnwise</code> which means results are in columns. <code>valuewise</code> means the results are in a single column (sqlite test style).</li> <li>parser: Added <code>valuesort</code>sort mode. The <code>valuesort</code> mode works like rowsort except that it does not honor row groupings. Each individual result value is sorted on its own.</li> </ul> <p><strong>Breaking change</strong>:</p> <ul> <li>The <code>Validator</code> type used in various function in Runner implementation has a new required field <code>Normalizer</code> that is used to normalize result values.</li> </ul> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/risinglightdb/sqllogictest-rs/blob/main/CHANGELOG.md";>sqllogictest's changelog</a>.</em></p> <blockquote> <h2>[0.24.0] - 2024-12-20</h2> <ul> <li>runner: Added a <code>Normalizer</code> type for normalizing result values. A new function <code>with_normalizer(normalizer: Normalizer)</code> has been added to the Runner to allow for specifying a custom Normalizer. The existing default normalizer is available via the <code>runner::default_normalizer(..)</code> function.</li> <li>parser: Added a new control mode <code>resultmode</code> that controls whether the results are in <code>valuewise</code> or <code>columnwise</code> mode. The default is <code>columnwise</code> which means results are in columns. <code>valuewise</code> means the results are in a single column (sqlite test style).</li> <li>parser: Added <code>valuesort</code>sort mode. The <code>valuesort</code> mode works like rowsort except that it does not honor row groupings. Each individual result value is sorted on its own.</li> </ul> <p><strong>Breaking change</strong>:</p> <ul> <li>The <code>Validator</code> type used in various function in Runner implementation has a new required field <code>Normalizer</code> that is used to normalize result values.</li> </ul> <h2>[0.23.1] - 2024-12-13</h2> <ul> <li>feat(bin): add opt <code>--keep-db-on-failure</code></li> </ul> <h2>[0.23.0] - 2024-11-16</h2> <ul> <li>Refine the behavior of <code>update_record_with_output</code> / <code>--override</code> <ul> <li>runner: Previously, <code>query</code> returning 0 rows will become <code>statement ok</code>. Now it returns <code>statement count 0</code>.</li> <li>bin: Now <code>--override</code> will not change the type chars of <code>query <types></code>, since in practice it becomes <code>?</code>s which might cause confusion.</li> </ul> </li> <li>runner: <code>statement count <n></code> is incorrectly handled when the result is a <code>query</code>.</li> </ul> <h2>[0.22.1] - 2024-11-11</h2> <ul> <li>engines/bin: fix compatibility with the new tokio-postgres minor version.</li> </ul> <h2>[0.22.0] - 2024-09-09</h2> <ul> <li>engines/bin: support MySQL engine</li> </ul> <h2>[0.21.0] - 2024-06-30</h2> <p><strong>Breaking changes</strong>:</p> <ul> <li>runner: <code>RecordOutput</code> is now returned by <code>Runner::run</code> (or <code>Runner::run_async</code>). This allows users to access the output of each record, or check whether the record is skipped.</li> <li>runner(substitution): add a special variable <code>__NOW__</code> which will be replaced with the current Unix timestamp in nanoseconds.</li> <li>runner(substitution): for <code>system</code> commands, we do not substitute environment variables any more, because the shell can do that. It's necessary to escape like <code>\\</code> any more. <code>$__TEST_DIR__</code>, and are still supported.</li> <li>runner(system): change <code>sh</code> to <code>bash</code>.</li> </ul> <h2>[0.20.6] - 2024-06-21</h2> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/risinglightdb/sqllogictest-rs/commit/ac188cb6790a5febbceee44f82879b8bbf15da25";><code>ac188cb</code></a> Add valuesort, new control result mode and value normalizer (<a href="https://redirect.github.com/risinglightdb/sqllogictest-rs/issues/237";>#237</a>)</li> <li><a href="https://github.com/risinglightdb/sqllogictest-rs/commit/e08bc0679d1e9aaf64143cb611369eaec44d2a4b";><code>e08bc06</code></a> feat(bin): add opt <code>--keep-db-on-failure</code> (<a href="https://redirect.github.com/risinglightdb/sqllogictest-rs/issues/236";>#236</a>)</li> <li>See full diff in <a href="https://github.com/risinglightdb/sqllogictest-rs/compare/v0.23.0...v0.24.0";>compare view</a></li> </ul> </details> <br /> 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 merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@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: github-unsubscr...@datafusion.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: github-unsubscr...@datafusion.apache.org For additional commands, e-mail: github-h...@datafusion.apache.org
