Update databricks-labs-lsql requirement from <0.14,>=0.5 to >=0.5,<0.15 (#3321)

Fix #3307
Fix #3306
Fix #3303
Fix #3302
Fix #3301
Fix #3300
Fix #3299
Fix #3298
Fix #3297
Fix #3296
Fix #3295
Fix #3294
Fix #3293
Fix #3292
Fix #3291
Fix #3290
Fix #3289
Fix #3288
Fix #3287
Fix #3286
Fix #3285
Fix #3284
Fix #3283
Fix #3282
Fix #3281
Fix #3280 
Fix #3279
Fix #3278
Fix #3277
Fix #3276

Updates the requirements on
[databricks-labs-lsql](https://github.com/databrickslabs/lsql) to permit
the latest version.
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a
href="https://github.com/databrickslabs/lsql/releases">databricks-labs-lsql's
releases</a>.</em></p>
<blockquote>
<h2>v0.14.0</h2>
<ul>
<li>Added nightly tests run at 4:45am UTC (<a
href="https://redirect.github.com/databrickslabs/lsql/issues/318">#318</a>).
A new nightly workflow has been added to the codebase, designed to
automate a series of jobs every day at 4:45am UTC on the
<code>larger</code> environment. The workflow includes permissions for
writing id-tokens, accessing issues, reading contents and pull-requests.
It checks out the code with a full fetch-depth, installs Python 3.10,
and uses hatch 1.9.4. The key step in this workflow is the execution of
nightly tests using the databrickslabs/sandbox/acceptance action, which
creates issues if necessary. The workflow utilizes several secrets,
including VAULT_URI, GITHUB_TOKEN, ARM_CLIENT_ID, and ARM_TENANT_ID, and
sets the TEST_NIGHTLY environment variable to true. Additionally, the
workflow is part of a concurrency group called
&quot;single-acceptance-job-per-repo&quot;, ensuring that only one
acceptance job runs at a time per repository.</li>
<li>Bump codecov/codecov-action from 4 to 5 (<a
href="https://redirect.github.com/databrickslabs/lsql/issues/319">#319</a>).
In this version update, the Codecov GitHub Action has been upgraded from
4 to 5, bringing improved functionality and new features. This new
version utilizes the Codecov Wrapper to encapsulate the CLI, enabling
faster updates. Additionally, an opt-out feature has been introduced for
tokens in public repositories, allowing contributors and other members
to upload coverage reports without requiring access to the Codecov
token. The upgrade also includes changes to the arguments:
<code>file</code> is now deprecated and replaced with
<code>files</code>, and <code>plugin</code> is deprecated and replaced
with <code>plugins</code>. New arguments have been added, including
<code>binary</code>, <code>gcov_args</code>,
<code>gcov_executable</code>, <code>gcov_ignore</code>,
<code>gcov_include</code>, <code>report_type</code>,
<code>skip_validation</code>, and <code>swift_project</code>.
Comprehensive documentation on these changes can be found in the release
notes and changelog.</li>
<li>Fixed <code>RuntimeBackend</code> exception handling (<a
href="https://redirect.github.com/databrickslabs/lsql/issues/328">#328</a>).
In this release, we have made significant improvements to the exception
handling in the <code>RuntimeBackend</code> component, addressing issues
reported in tickets <a
href="https://redirect.github.com/databrickslabs/lsql/issues/328">#328</a>,
<a
href="https://redirect.github.com/databrickslabs/lsql/issues/327">#327</a>,
<a
href="https://redirect.github.com/databrickslabs/lsql/issues/326">#326</a>,
and <a
href="https://redirect.github.com/databrickslabs/lsql/issues/325">#325</a>.
We have updated the <code>execute</code> and <code>fetch</code> methods
to handle exceptions more gracefully and changed exception handling from
catching <code>Exception</code> to catching <code>BaseException</code>
for more comprehensive error handling. Additionally, we have updated the
<code>pyproject.toml</code> file to use a newer version of the
<code>databricks-labs-pytester</code> package (0.2.1 to 0.5.0) which may
have contributed to the resolution of these issues. Furthermore, the
<code>test_backends.py</code> file has been updated to improve the
readability and user-friendliness of the test output for the functions
testing if a <code>NotFound</code>, <code>BadRequest</code>, or
<code>Unknown</code> exception is raised when executing and fetching
statements. The <code>test_runtime_backend_use_statements</code>
function has also been updated to print <code>PASSED</code> or
<code>FAILED</code> instead of returning those values. These changes
enhance the robustness of the exception handling mechanism in the
<code>RuntimeBackend</code> class and update related unit tests.</li>
</ul>
<p>Dependency updates:</p>
<ul>
<li>Bump codecov/codecov-action from 4 to 5 (<a
href="https://redirect.github.com/databrickslabs/lsql/pull/319">#319</a>).</li>
</ul>
<p>Contributors: <a
href="https://github.com/nfx"><code>@​nfx</code></a>, <a
href="https://github.com/JCZuurmond"><code>@​JCZuurmond</code></a>, <a
href="https://github.com/dependabot"><code>@​dependabot</code></a>[bot]</p>
</blockquote>
</details>
<details>
<summary>Changelog</summary>
<p><em>Sourced from <a
href="https://github.com/databrickslabs/lsql/blob/main/CHANGELOG.md">databricks-labs-lsql's
changelog</a>.</em></p>
<blockquote>
<h2>0.14.0</h2>
<ul>
<li>Added nightly tests run at 4:45am UTC (<a
href="https://redirect.github.com/databrickslabs/lsql/issues/318">#318</a>).
A new nightly workflow has been added to the codebase, designed to
automate a series of jobs every day at 4:45am UTC on the
<code>larger</code> environment. The workflow includes permissions for
writing id-tokens, accessing issues, reading contents and pull-requests.
It checks out the code with a full fetch-depth, installs Python 3.10,
and uses hatch 1.9.4. The key step in this workflow is the execution of
nightly tests using the databrickslabs/sandbox/acceptance action, which
creates issues if necessary. The workflow utilizes several secrets,
including VAULT_URI, GITHUB_TOKEN, ARM_CLIENT_ID, and ARM_TENANT_ID, and
sets the TEST_NIGHTLY environment variable to true. Additionally, the
workflow is part of a concurrency group called
&quot;single-acceptance-job-per-repo&quot;, ensuring that only one
acceptance job runs at a time per repository.</li>
<li>Bump codecov/codecov-action from 4 to 5 (<a
href="https://redirect.github.com/databrickslabs/lsql/issues/319">#319</a>).
In this version update, the Codecov GitHub Action has been upgraded from
4 to 5, bringing improved functionality and new features. This new
version utilizes the Codecov Wrapper to encapsulate the CLI, enabling
faster updates. Additionally, an opt-out feature has been introduced for
tokens in public repositories, allowing contributors and other members
to upload coverage reports without requiring access to the Codecov
token. The upgrade also includes changes to the arguments:
<code>file</code> is now deprecated and replaced with
<code>files</code>, and <code>plugin</code> is deprecated and replaced
with <code>plugins</code>. New arguments have been added, including
<code>binary</code>, <code>gcov_args</code>,
<code>gcov_executable</code>, <code>gcov_ignore</code>,
<code>gcov_include</code>, <code>report_type</code>,
<code>skip_validation</code>, and <code>swift_project</code>.
Comprehensive documentation on these changes can be found in the release
notes and changelog.</li>
<li>Fixed <code>RuntimeBackend</code> exception handling (<a
href="https://redirect.github.com/databrickslabs/lsql/issues/328">#328</a>).
In this release, we have made significant improvements to the exception
handling in the <code>RuntimeBackend</code> component, addressing issues
reported in tickets <a
href="https://redirect.github.com/databrickslabs/lsql/issues/328">#328</a>,
<a
href="https://redirect.github.com/databrickslabs/lsql/issues/327">#327</a>,
<a
href="https://redirect.github.com/databrickslabs/lsql/issues/326">#326</a>,
and <a
href="https://redirect.github.com/databrickslabs/lsql/issues/325">#325</a>.
We have updated the <code>execute</code> and <code>fetch</code> methods
to handle exceptions more gracefully and changed exception handling from
catching <code>Exception</code> to catching <code>BaseException</code>
for more comprehensive error handling. Additionally, we have updated the
<code>pyproject.toml</code> file to use a newer version of the
<code>databricks-labs-pytester</code> package (0.2.1 to 0.5.0) which may
have contributed to the resolution of these issues. Furthermore, the
<code>test_backends.py</code> file has been updated to improve the
readability and user-friendliness of the test output for the functions
testing if a <code>NotFound</code>, <code>BadRequest</code>, or
<code>Unknown</code> exception is raised when executing and fetching
statements. The <code>test_runtime_backend_use_statements</code>
function has also been updated to print <code>PASSED</code> or
<code>FAILED</code> instead of returning those values. These changes
enhance the robustness of the exception handling mechanism in the
<code>RuntimeBackend</code> class and update related unit tests.</li>
</ul>
<p>Dependency updates:</p>
<ul>
<li>Bump codecov/codecov-action from 4 to 5 (<a
href="https://redirect.github.com/databrickslabs/lsql/pull/319">#319</a>).</li>
</ul>
<h2>0.13.0</h2>
<ul>
<li>Added <code>escape_name</code> function to escape individual SQL
names and <code>escape_full_name</code> function to escape dot-separated
full names (<a
href="https://redirect.github.com/databrickslabs/lsql/issues/316">#316</a>).
Two new functions, <code>escape_name</code> and
<code>escape_full_name</code>, have been added to the
<code>databricks.labs.lsql.escapes</code> module for escaping SQL names.
The <code>escape_name</code> function takes a single name as an input
and returns it enclosed in backticks, while
<code>escape_full_name</code> handles dot-separated full names by
escaping each individual component. These functions have been ported
from the <code>databrickslabs/ucx</code> repository and are designed to
provide a consistent way to escape names and full names in SQL
statements, improving the robustness of the system by preventing issues
caused by unescaped special characters in SQL names. The test suite
includes various cases, including single names, full names with
different combinations of escaped and unescaped components, and special
characters, with a specific focus on the scenario where the column name
contains a period.</li>
<li>Bump actions/checkout from 4.2.0 to 4.2.1 (<a
href="https://redirect.github.com/databrickslabs/lsql/issues/304">#304</a>).
In this pull request, the <code>actions/checkout</code> dependency is
updated from version 4.2.0 to 4.2.1 in the
<code>.github/workflows/release.yml</code> file. This update includes a
new feature where <code>refs/*</code> are checked out by commit if
provided, falling back to the ref specified by the
<code>@orhantoy</code> user. This change improves the flexibility of the
action, allowing users to specify a commit or branch for checkout. The
pull request also introduces a new contributor, <code>@Jcambass</code>,
who added a workflow file for publishing releases to an immutable action
package. The commits for this release include changes to prepare for the
4.2.1 release, add a workflow file for publishing releases, and check
out other <code>refs/*</code> by commit if provided, falling back to
ref. This pull request has been reviewed and approved by
Dependabot.</li>
<li>Bump actions/checkout from 4.2.1 to 4.2.2 (<a
href="https://redirect.github.com/databrickslabs/lsql/issues/310">#310</a>).
This is a pull request to update the <code>actions/checkout</code>
dependency from version 4.2.1 to 4.2.2, which includes improvements to
the <code>url-helper.ts</code> file that now utilize well-known
environment variables and expanded unit test coverage for the
<code>isGhes</code> function. The <code>actions/checkout</code> action
is commonly used in GitHub Actions workflows for checking out a
repository at a specific commit or branch. The changes in this update
are internal to the <code>actions/checkout</code> action and should not
affect the functionality of the project utilizing this action. The pull
request also includes details on the commits and compatibility score for
the upgrade, and reviewers can manage and merge the request using
Dependabot commands once the changes have been verified.</li>
<li>Bump databrickslabs/sandbox from acceptance/v0.3.0 to 0.3.1 (<a
href="https://redirect.github.com/databrickslabs/lsql/issues/307">#307</a>).
In this release, the <code>databrickslabs/sandbox</code> dependency has
been updated from version <code>acceptance/v0.3.0</code> to
<code>0.3.1</code>. This update includes previously tagged commits, bug
fixes for git-related libraries, and resolution of the <code>unsupported
protocol scheme</code> error. The README has been updated with more
information on using the <code>databricks labs sandbox</code> command,
and installation instructions have been improved. Additionally, there
have been dependency updates for <code>go-git</code> libraries and
<code>golang.org/x/crypto</code> in the <code>/go-libs</code> and
<code>/runtime-packages</code> directories. New commits in this release
allow larger logs from acceptance tests and implement experimental OIDC
refresh functionality. Ignore conditions have been applied to prevent
conflicts with previous versions of the dependency. This update is
recommended for users who want to take advantage of the latest bug fixes
and improvements.</li>
<li>Bump databrickslabs/sandbox from acceptance/v0.3.1 to 0.4.2 (<a
href="https://redirect.github.com/databrickslabs/lsql/issues/315">#315</a>).
In this release, the <code>databrickslabs/sandbox</code> dependency has
been updated from version <code>acceptance/v0.3.1</code> to
<code>0.4.2</code>. This update includes bug fixes, dependency updates,
and additional go-git libraries. Specifically, the <code>Run integration
tests</code> job in the GitHub Actions workflow has been updated to use
the new version of the <code>databrickslabs/sandbox/acceptance</code>
Docker image. The updated version also includes install instructions,
usage instructions in the README, and a modification to provide more
git-related libraries. Additionally, there were several updates to
dependencies, including <code>golang.org/x/crypto</code> version
<code>0.16.0</code> to <code>0.17.0</code>. Dependabot, a tool that
manages dependencies in GitHub projects, is responsible for the update
and provides instructions for resolving any conflicts or merging the
changes into the project. This update is intended to improve the
functionality and reliability of the <code>databrickslabs/sandbox</code>
dependency.</li>
<li>Deprecate <code>Row.as_dict()</code> (<a
href="https://redirect.github.com/databrickslabs/lsql/issues/309">#309</a>).
In this release, we are introducing a deprecation warning for the
<code>as_dict()</code> method in the <code>Row</code> class, which will
be removed in favor of the <code>asDict()</code> method. This change
aims to maintain consistency with Spark's <code>Row</code> behavior and
prevent subtle bugs when switching between different backends. The
deprecation warning will be implemented using Python's warnings
mechanism, including the new annotation in Python 3.13 for static code
analysis. The existing functionality of fetching values from the
database through <code>StatementExecutionExt</code> remains unchanged.
We recommend that clients update their code to use
<code>.asDict()</code> instead of <code>.as_dict()</code> to avoid any
disruptions. A new test case <code>test_row_as_dict_deprecated()</code>
has been added to verify the deprecation warning for
<code>Row.as_dict()</code>.</li>
<li>Minor improvements for
<code>.save_table(mode=&quot;overwrite&quot;)</code> (<a
href="https://redirect.github.com/databrickslabs/lsql/issues/298">#298</a>).
In this release, the <code>.save_table()</code> method has been
improved, particularly when using the <code>overwrite</code> mode. If no
rows are supplied, the table will now be truncated, ensuring consistency
with the mock backend behavior. This change has been optimized for
SQL-based backends, which now perform truncation as part of the insert
for the first batch. Type hints on the abstract method have been updated
to match the concrete implementations. Unit tests and integration tests
have been updated to cover the new functionality, and new methods have
been added to test the truncation behavior in overwrite mode. These
improvements enhance the consistency and efficiency of the
<code>.save_table()</code> method when using <code>overwrite</code> mode
across different backends.</li>
<li>Updated databrickslabs/sandbox requirement to acceptance/v0.3.0 (<a
href="https://redirect.github.com/databrickslabs/lsql/issues/305">#305</a>).
In this release, we have updated the requirement for the
<code>databrickslabs/sandbox</code> package to version
<code>acceptance/v0.3.0</code> in the <code>downstreams.yml</code> file.
This update is necessary to use the latest version of the package, which
includes several bug fixes and dependency updates. The
<code>databrickslabs/sandbox</code> package is used in the acceptance
tests, which are run as part of the CI/CD pipeline. It provides a set of
tools and utilities for developing and testing code in a sandbox
environment. The changelog for this version includes the addition of
install instructions, more git-related libraries, and the modification
of the README to include information about how to use it with the
<code>databricks labs sandbox</code> command. Specifically, the version
of the <code>databrickslabs/sandbox</code> package used in the
<code>acceptance</code> job has been updated from
<code>acceptance/v0.1.4</code> to <code>acceptance/v0.3.0</code>,
allowing the integration tests to be run using the latest version of the
package. The ignore conditions for this PR ensure that Dependabot will
resolve any conflicts that may arise and can be manually triggered with
the <code>@dependabot rebase</code> command.</li>
</ul>
<p>Dependency updates:</p>
<ul>
<li>Bump actions/checkout from 4.2.0 to 4.2.1 (<a
href="https://redirect.github.com/databrickslabs/lsql/pull/304">#304</a>).</li>
<li>Updated databrickslabs/sandbox requirement to acceptance/v0.3.0 (<a
href="https://redirect.github.com/databrickslabs/lsql/pull/305">#305</a>).</li>
<li>Bump databrickslabs/sandbox from acceptance/v0.3.0 to 0.3.1 (<a
href="https://redirect.github.com/databrickslabs/lsql/pull/307">#307</a>).</li>
<li>Bump actions/checkout from 4.2.1 to 4.2.2 (<a
href="https://redirect.github.com/databrickslabs/lsql/pull/310">#310</a>).</li>
<li>Bump databrickslabs/sandbox from acceptance/v0.3.1 to 0.4.2 (<a
href="https://redirect.github.com/databrickslabs/lsql/pull/315">#315</a>).</li>
</ul>
<h2>0.12.1</h2>
<ul>
<li>Bump actions/checkout from 4.1.7 to 4.2.0 (<a
href="https://redirect.github.com/databrickslabs/lsql/issues/295">#295</a>).
In this version 4.2.0 release of the <code>actions/checkout</code>
library, the team has added <code>Ref</code> and <code>Commit</code>
outputs, which provide the ref and commit that were checked out,
respectively. The update also includes dependency updates to
<code>braces</code>, <code>minor-npm-dependencies</code>,
<code>docker/build-push-action</code>, and
<code>docker/login-action</code>, all of which were automatically
resolved by Dependabot. These updates improve compatibility and
stability for users of the library. This release is a result of
contributions from new team members <a
href="https://github.com/yasonk"><code>@​yasonk</code></a> and <a
href="https://github.com/lucacome"><code>@​lucacome</code></a>. Users
can find a detailed commit history, pull requests, and release notes in
the associated links. The team strongly encourages all users to upgrade
to this new version to access the latest features and improvements.</li>
<li>Set catalog on <code>SchemaDeployer</code> to overwrite the default
<code>hive_metastore</code> (<a
href="https://redirect.github.com/databrickslabs/lsql/issues/296">#296</a>).
In this release, the default catalog for <code>SchemaDeployer</code> has
been changed from <code>hive_metastore</code> to a user-defined catalog,
allowing for more flexibility in deploying resources to different
catalogs. A new dependency, <code>databricks-labs-pytester</code>, has
been added with a version constraint of <code>&gt;=0.2.1</code>, which
may indicate the introduction of new testing functionality. The
<code>SchemaDeployer</code> class has been updated to accept a
<code>catalog</code> parameter and the tests for deploying and deleting
schemas, tables, and views have been updated to reflect these changes.
The <code>test_deploys_schema</code>,
<code>test_deploys_dataclass</code>, and <code>test_deploys_view</code>
tests have been updated to accept a <code>inventory_catalog</code>
parameter, and the <code>caplog</code> fixture is used to capture log
messages and assert that they contain the expected messages.
Additionally, a new test function
<code>test_statement_execution_backend_overwrites_table</code> has been
added to the <code>tests/integration/test_backends.py</code> file to
test the functionality of the <code>StatementExecutionBackend</code>
class in overwriting a table in the database and retrieving the correct
data. Issue <a
href="https://redirect.github.com/databrickslabs/lsql/issues/294">#294</a>
has been resolved, and progress has been made on issue <a
href="https://redirect.github.com/databrickslabs/lsql/issues/278">#278</a>,
but issue <a
href="https://redirect.github.com/databrickslabs/lsql/issues/280">#280</a>
has been marked as technical debt and issue <a
href="https://redirect.github.com/databrickslabs/lsql/issues/287">#287</a>
is required for the CI to pass.</li>
</ul>
<p>Dependency updates:</p>
<ul>
<li>Bump actions/checkout from 4.1.7 to 4.2.0 (<a
href="https://redirect.github.com/databrickslabs/lsql/pull/295">#295</a>).</li>
</ul>
<h2>0.12.0</h2>
<ul>
<li>Added method to detect rows are written to the
<code>MockBackend</code> (<a
href="https://redirect.github.com/databrickslabs/lsql/issues/292">#292</a>).
In this commit, the <code>MockBackend</code> class in the 'backends.py'
file has been updated with a new method, 'has_rows_written_for', which
allows for differentiation between a table that has never been written
to and one with zero rows. This method checks if a specific table has
been written to by iterating over the table stubs in the
<code>_save_table</code> attribute and returning <code>True</code> if
the given full name matches any of the stub full names. Additionally,
the class has been supplemented with the <code>rows_written_for</code>
method, which takes a table name and mode as input and returns a list of
rows written to that table in the given mode. Furthermore, several new
test cases have been added to test the functionality of the
<code>MockBackend</code> class, including checking if the
<code>has_rows_written_for</code> method correctly identifies when there
are no rows written, when there are zero rows written, and when rows are
written after the first and second write operations. These changes
improve the overall testing coverage of the project and aid in testing
the functionality of the <code>MockBackend</code> class. The new methods
are accompanied by documentation strings that explain their purpose and
functionality.</li>
</ul>
<h2>0.11.0</h2>
<ul>
<li>Added filter spec implementation (<a
href="https://redirect.github.com/databrickslabs/lsql/issues/276">#276</a>).
In this commit, a new <code>FilterHandler</code> class has been
introduced to handle filter files with the suffix
<code>.filter.json</code>, which can parse filter specifications in the
header of the filter file and validate the filter columns and types. The
commit also adds support for three types of filters:
<code>DATE_RANGE_PICKER</code>, <code>MULTI_SELECT</code>, and
<code>DROPDOWN</code>, which can be linked with multiple visualization
widgets. Additionally, a <code>FilterTile</code> class has been added to
the <code>Tile</code> class, which represents a filter tile in the
dashboard and includes methods to validate the tile, create widgets, and
generate filter encodings and queries. The
<code>DashboardMetadata</code> class has been updated to include a new
method <code>get_datasets()</code> to retrieve the datasets for the
dashboard. These changes enhance the functionality of the dashboard by
adding support for filtering data using various filter types and linking
them with multiple visualization widgets, improving the customization
and interactivity of the dashboard, and making it more user-friendly and
efficient.</li>
<li>Bugfix: <code>MockBackend</code> wasn't mocking
<code>savetable</code> properly when the mode is <code>append</code> (<a
href="https://redirect.github.com/databrickslabs/lsql/issues/289">#289</a>).
This release includes a bugfix and enhancements for the
<code>MockBackend</code> component, which is used to mock the
<code>SQLBackend</code>. The <code>.savetable()</code> method failed to
function as expected in <code>append</code> mode, writing all rows to
the same table instead of accumulating them. This bug has been
addressed, ensuring that rows accumulate correctly in
<code>append</code> mode. Additionally, a new test function,
<code>test_mock_backend_save_table_overwrite()</code>, has been added to
demonstrate the corrected behavior of <code>overwrite</code> mode,
showing that it now replaces only the existing rows for the given table
while preserving other tables' contents. The type signature for
<code>.save_table()</code> has been updated, restricting the
<code>mode</code> parameter to accept only two string literals:
<code>&quot;append&quot;</code> and <code>&quot;overwrite&quot;</code>.
The <code>MockBackend</code> behavior has been updated accordingly, and
rows are now filtered to exclude any <code>None</code> or
<code>NULL</code> values prior to saving. These improvements to the
<code>MockBackend</code> functionality and test suite increase
reliability when using the <code>MockBackend</code> as a testing backend
for the system.</li>
<li>Changed filter spec to use YML instead of JSON (<a
href="https://redirect.github.com/databrickslabs/lsql/issues/290">#290</a>).
In this release, the filter specification files have been converted from
JSON to YAML format, providing a more human-readable format for the
filter specifications. The schema for the filter file includes flags for
column, columns, type, title, description, order, and id, with the type
flag taking on values of DROPDOWN, MULTI_SELECT, or DATE_RANGE_PICKER.
This change impacts the FilterHandler, is_filter method, and
_from_dashboard_folder method, as well as relevant parts of the
documentation. Additionally, the parsing methods have been updated to
use yaml.safe_load instead of json.loads, and the is_filter method now
checks for .filter.yml suffix. A new file, '00_0_date.filter.yml', has
been added to the 'tests/integration/dashboards/filter_spec_basic'
directory, containing a sample date filter definition. Furthermore,
various tests have been added to validate filter specifications, such as
checking for invalid type and both <code>column</code> and
<code>columns</code> keys being present. These updates aim to enhance
readability, maintainability, and ease of use for filter
configuration.</li>
<li>Increase testing of generic types storage (<a
href="https://redirect.github.com/databrickslabs/lsql/issues/282">#282</a>).
A new commit enhances the testing of generic types storage by expanding
the test suite to include a list of structs, ensuring more comprehensive
testing of the system. The <code>Foo</code> struct has been renamed to
<code>Nested</code> for clarity, and two new structs,
<code>NestedWithDict</code> and <code>Nesting</code>, have been added.
The <code>Nesting</code> struct contains a <code>Nested</code> object,
while <code>NestedWithDict</code> includes a string and an optional
dictionary of strings. A new test case demonstrates appending complex
types to a table by creating and saving a table with two rows, each
containing a <code>Nesting</code> struct. The test then fetches the data
and asserts the expected number of rows are returned, ensuring the
proper functioning of the storage system with complex data types.</li>
<li>Minor Changes to avoid redundancy in code and follow code patterns
(<a
href="https://redirect.github.com/databrickslabs/lsql/issues/279">#279</a>).
In this release, we have made significant improvements to the
<code>dashboards.py</code> file to make the code more concise,
maintainable, and in line with the standard library's recommended usage.
The <code>export_to_zipped_csv</code> method has undergone major
changes, including the removal of the <code>BytesIO</code> module import
and the use of <code>StringIO</code> for handling strings as files. The
method no longer creates a separate ZIP file for the CSV files, instead
using the provided <code>export_path</code>. Additionally, the method
skips tiles that don't contain queries. We have also introduced a new
method, <code>dataclass_transform</code>, which transforms a given
dataclass into a new one with specific attributes and behavior. This
method creates a new dataclass with a custom metaclass and adds a new
method, <code>to_dict()</code>, which converts the instances of the new
dataclass to dictionaries. These changes promote code reusability and
reduce redundancy in the codebase, making it easier for software
engineers to work with.</li>
</ul>
<!-- raw HTML omitted -->
</blockquote>
<p>... (truncated)</p>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a
href="https://github.com/databrickslabs/lsql/commit/383bb807167758e1eb47fceee8dfc8df5ad7bb32"><code>383bb80</code></a>
Release v0.14.0 (<a
href="https://redirect.github.com/databrickslabs/lsql/issues/329">#329</a>)</li>
<li><a
href="https://github.com/databrickslabs/lsql/commit/7ba1ca04fd581fa69d74437a6613690e896cbd80"><code>7ba1ca0</code></a>
Fixed <code>RuntimeBackend</code> exception handling (<a
href="https://redirect.github.com/databrickslabs/lsql/issues/328">#328</a>)</li>
<li><a
href="https://github.com/databrickslabs/lsql/commit/4f5ef749f48d6e9a593cfca7c3fd9ddf889f7d7e"><code>4f5ef74</code></a>
Added nightly tests run at 4:45am UTC (<a
href="https://redirect.github.com/databrickslabs/lsql/issues/318">#318</a>)</li>
<li><a
href="https://github.com/databrickslabs/lsql/commit/5bcb6cc7fe86eb5d0ea16fa6f437e850c56e0a1a"><code>5bcb6cc</code></a>
Bump codecov/codecov-action from 4 to 5 (<a
href="https://redirect.github.com/databrickslabs/lsql/issues/319">#319</a>)</li>
<li><a
href="https://github.com/databrickslabs/lsql/commit/69c6e975cecb6505e6e61e5e18204fea9d1fea1f"><code>69c6e97</code></a>
Handle changes from Databricks Python SDK 0.37.0 (<a
href="https://redirect.github.com/databrickslabs/lsql/issues/320">#320</a>)</li>
<li><a
href="https://github.com/databrickslabs/lsql/commit/48c287e9fe2910926a4f498e3f5474c496c454da"><code>48c287e</code></a>
Release v0.13.0 (<a
href="https://redirect.github.com/databrickslabs/lsql/issues/317">#317</a>)</li>
<li><a
href="https://github.com/databrickslabs/lsql/commit/776e1cfbca5aa0de5e3790c0cbad5b41ee8b8c8e"><code>776e1cf</code></a>
Added <code>escape_name</code> function to escape individual SQL names
and `escape_full_...</li>
<li><a
href="https://github.com/databrickslabs/lsql/commit/aae9ea16d4ccbc206ca268883c648e3ff91b845f"><code>aae9ea1</code></a>
Bump databrickslabs/sandbox from acceptance/v0.3.1 to 0.4.2 (<a
href="https://redirect.github.com/databrickslabs/lsql/issues/315">#315</a>)</li>
<li><a
href="https://github.com/databrickslabs/lsql/commit/9aace9e4d27828f46bc9c558b7b76f77ff6fd19a"><code>9aace9e</code></a>
Deprecate <code>Row.as_dict()</code> (<a
href="https://redirect.github.com/databrickslabs/lsql/issues/309">#309</a>)</li>
<li><a
href="https://github.com/databrickslabs/lsql/commit/94ed7f0bb9854d1b9955060d4a995b171b5ef630"><code>94ed7f0</code></a>
Bump actions/checkout from 4.2.1 to 4.2.2 (<a
href="https://redirect.github.com/databrickslabs/lsql/issues/310">#310</a>)</li>
<li>Additional commits viewable in <a
href="https://github.com/databrickslabs/lsql/compare/v0.5.0...v0.14.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>

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

Author: dependabot[bot]

pyproject.toml

@@ -45,7 +45,7 @@ classifiers = [
 ]
 
 dependencies = ["databricks-sdk~=0.36",
-                "databricks-labs-lsql>=0.5,<0.14",
+                "databricks-labs-lsql>=0.5,<0.15",
                 "databricks-labs-blueprint>=0.9.1,<0.10",
                 "PyYAML>=6.0.0,<7.0.0",
                 "sqlglot>=25.5.0,<25.30",