Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
databricks.labs.lsql.core
module has been updated to handle nullable values correctly. A new methodStatementExecutionExt
has been added, which manages the handling of nullable values during SQL statement execution. TheRow
class has also been modified to include nullable values, improving the robustness and flexibility of SQL execution in dealing with various data types, including null values. These enhancements increase the overall reliability of the system, making it more production-ready.make_random()
, has been added to theconftest.py
file to generate a random string of fixed length, aiding in the creation of more meaningful and readable random strings for integration tests. A new file,test_deployment.py
, has been introduced, containing a test function for deploying a database schema and verifying successful data retrieval via a view. Thetest_integration.py
file has been renamed totest_core.py
, with updates to thetest_fetch_one
function to test thefetch_one
method using a SQL query with an aliased value. Additionally, a newFoo
dataclass has been added to thetests/integration/views/__init__.py
file, supporting integration test coverage. Lastly, a new SQL query has been added to the integration test suite, located in thesome.sql
file, which retrieves data from a table namedfoo
in theinventory
schema. These changes aim to enhance the overall stability, reliability, and coverage of the project's integration tests. Note: The changes to the.gitignore
file and the improvements to theStatementExecutionBackend
class in thebackends.py
file are not included in this summary, as they were described in the opening statement.hatch
being present on the build machine (#54). In this release, we have made significant changes to how we manage our build process and toolchain configuration. We have removed the need to manually installhatch
version 1.7.0 in the build machine, and instead, rely on its presence, adding it to the list of required tools in the toolchain configuration. The command to create a virtual environment usinghatch
has also been added, and thepre_setup
section no longer includes installinghatch
, assuming its availability. We have also updated thehatch
package version from 1.7.0 to 1.9.4, which may include bug fixes, performance improvements, or new features. This change may impact the behavior of any existing functionality that relies onhatch
. Thepyproject.toml
file has been modified to update thefmt
andverify
sections, withruff check . --fix
replacingruff . --fix
and the removal ofblack --check .
andisort . --check-only
. A new configuration forisort
has also been added to specify thedatabricks.labs.blueprint
package as a known first-party package, enabling more precise management of imports related to that package. These changes simplify the build process and ensure that the project is using a more recent version of thehatch
package for packaging and distributing Python projects.sqlglot
package in our project'spyproject.toml
file. Previously, we had set the constraint to~=22.3.1
, allowing for any version with the same major and minor numbers but different patch numbers. With this update, we have changed the constraint to>=22.3.1,<22.5.0
. This change enables our project to utilize bug fixes and improvements made in the latest patch versions ofsqlglot
, while still preventing it from inadvertently using any breaking changes introduced in version 22.5.0 or later versions. This modification allows us to take advantage of the latest features and improvements insqlglot
while maintaining compatibility and stability in our project.Dependency updates: