Skip to content

Conversation

@msrathore-db
Copy link
Contributor

Description

Added a connection param of DecimalColumnScale. The parameter is not used in the code since the thrift server gives the default scale to the DECIMAL columns already. The default value provided is 0. So this function does not override it.

PECO-2733

@github-actions github-actions bot added this to the ADBC Libraries 21 milestone Sep 24, 2025
@msrathore-db msrathore-db changed the title Added decimalColumnScale connection param Feat(csharp/src/drivers/Databricks): Added decimalColumnScale connection param Sep 24, 2025
@msrathore-db msrathore-db changed the title Feat(csharp/src/drivers/Databricks): Added decimalColumnScale connection param feat(csharp/src/drivers/Databricks): Added decimalColumnScale connection param Sep 24, 2025
/// <summary>
/// Gets the decimal column scale value.
/// </summary>
public int DecimalColumnScale => _decimalColumnScale;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

where will this being used?

Copy link
Contributor Author

@msrathore-db msrathore-db Sep 24, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As explained in the jira, this param was not actually being used in ODBC and simba JDBC either since thrift already provides a default scale of 0.
I'll run test on different spark versions to see any changes.
Once confirmed for the other DBR versions, I can complete this PR.

@msrathore-db msrathore-db marked this pull request as draft September 24, 2025 17:34
@CurtHagenlocher CurtHagenlocher changed the title feat(csharp/src/drivers/Databricks): Added decimalColumnScale connection param feat(csharp/src/Drivers/Databricks): Added decimalColumnScale connection param Sep 24, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants