Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix 17 Add support for i128 #48

Merged
merged 1 commit into from
Jun 27, 2022
Merged

Fix 17 Add support for i128 #48

merged 1 commit into from
Jun 27, 2022

Conversation

ncpenke
Copy link
Collaborator

@ncpenke ncpenke commented Jun 27, 2022

No description provided.

@ncpenke ncpenke merged commit ef061fe into main Jun 27, 2022
@ncpenke ncpenke deleted the ncpenke/features branch June 27, 2022 23:01

#[inline]
fn data_type() -> arrow2::datatypes::DataType {
arrow2::datatypes::DataType::Decimal(32, 32)
Copy link
Collaborator

Choose a reason for hiding this comment

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

note that this is just the default. In general the user needs to specify the correct precision and scale via e.g. .to(DataType::Decimal(10, 11))

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Oh good point - what would you recommend for this? One idea is we could provide a datatype override for a field to override the default.

Copy link
Collaborator

Choose a reason for hiding this comment

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

yeap, I would recommend an override (ideally mandatory), so that people do not mistakenly use 32, 32 without thinking about it. If not possible mandatory, always present the override in the examples so people do not forget about it.

@ncpenke ncpenke mentioned this pull request Jun 27, 2022
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.

None yet

2 participants