Implemented the DECLARE VARIABLE feature for Oracle variable declarations. #1856
+239
−0
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.
Add DECLARE VARIABLE support for Oracle variable declarations (#762 )
Summary
This PR introduces support for Oracle-style variable declarations using the
DECLARE VARIABLE
syntax in the transpiler. It enhances compatibility with Databricks by mapping Oracle types to their appropriate equivalents and ensures backward compatibility with existing functionality.Problem Solved
Before:
p_date_start NUMBER;
→p_date_start AS NUMBER
After:
p_date_start NUMBER;
→DECLARE VARIABLE p_date_start BIGINT
Implementation Details
_oracle_variable_declaration_sql()
todatabricks.py
to detect Oracle variable declarations.TRANSFORMS
dictionary to handleexp.Alias
expressions.Oracle Type Mappings
Testing
test_oracle_variable_declarations.py
test_variable_declarations/
test_variable_declarations_1.sql
test_variable_declarations_1.databricks.sql
Key Features
Closes #762