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

Makes type casting consistent with schema. #69

Merged
merged 2 commits into from
Oct 1, 2015
Merged

Makes type casting consistent with schema. #69

merged 2 commits into from
Oct 1, 2015

Conversation

steventebrinke
Copy link
Contributor

For FoxPro databases the returned type differed from the reported schema, which was confusing.

For FoxPro databases the returned type differed from the reported schema, which was confusing.
@infused infused merged commit 8d97c5f into infused:master Oct 1, 2015
@infused
Copy link
Owner

infused commented Oct 1, 2015

Previously, we were returning an integer if the Double's number of decimals was set to 0. According the the Foxpro documentation:

When the Double data type is used in a table, the number of decimals specified when the field is created is for display purposes only.

This pull request ensures that we always return the Double's full precision.

@infused
Copy link
Owner

infused commented Oct 1, 2015

Thanks Steven, I've merged your commits and have released version 2.0.11.

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.

2 participants