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

SQLite: Consider changing ultimate fallback type to BLOB #13253

Closed
bricelam opened this issue Sep 7, 2018 · 0 comments · Fixed by #15071
Closed

SQLite: Consider changing ultimate fallback type to BLOB #13253

bricelam opened this issue Sep 7, 2018 · 0 comments · Fixed by #15071
Assignees
Labels
breaking-change closed-fixed The issue has been fixed and is/will be included in the release indicated by the issue milestone. type-enhancement
Milestone

Comments

@bricelam
Copy link
Contributor

bricelam commented Sep 7, 2018

We have #8824 to generally improve type inference, but we'll still have fallbacks. Like aspnet/Microsoft.Data.Sqlite#548, we should also review everywhere we fallback to a default and make sure it's consistent. I propose BLOB since every value can be losslessly coerced to it.

@bricelam bricelam self-assigned this Sep 7, 2018
@ajcvickers ajcvickers added this to the 3.0.0 milestone Sep 7, 2018
@bricelam bricelam added the closed-fixed The issue has been fixed and is/will be included in the release indicated by the issue milestone. label Mar 18, 2019
bricelam added a commit that referenced this issue Mar 19, 2019
It was previously a mixture of INTEGER and TEXT.

Resolves #13253, resolves #13841
@ajcvickers ajcvickers modified the milestones: 3.0.0, 3.0.0-preview4 Apr 15, 2019
@ajcvickers ajcvickers modified the milestones: 3.0.0-preview4, 3.0.0 Nov 11, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
breaking-change closed-fixed The issue has been fixed and is/will be included in the release indicated by the issue milestone. type-enhancement
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants