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: Better error messages (rather than "SQL logic error or missing database") #212

Closed
rowanmiller opened this issue May 22, 2014 · 8 comments
Assignees
Labels
closed-fixed The issue has been fixed and is/will be included in the release indicated by the issue milestone. type-bug
Milestone

Comments

@rowanmiller
Copy link
Contributor

No description provided.

@julielerman
Copy link

oh yes, i like this one. I have seen this error quite a few times today ;)

@bricelam
Copy link
Contributor

I dug into this a bit more, and there doesn't appear to be any way to get more detailed error messages from the native API. I'll keep looking though.

@julielerman
Copy link

well when more of the API is fleshed out, there will probably be less of these errors. :) I was trying to call savechanges & savechangesasync and new that the db was there since I was looking at it in file explorer after calling Create(). :)

@bricelam
Copy link
Contributor

lol true, If we'd just stop generating invalid SQL... 😉

@rowanmiller rowanmiller modified the milestones: Backlog, 7.0.0 Nov 26, 2014
@bricelam
Copy link
Contributor

bricelam commented Apr 9, 2015

I figured it out! sqlite3_errmsg returns better messages for syntax errors.

@bricelam bricelam self-assigned this Apr 9, 2015
@julielerman
Copy link

like

@ErikEJ
Copy link
Contributor

ErikEJ commented Apr 10, 2015

👍

@bricelam bricelam modified the milestone: Backlog Apr 16, 2015
@bricelam
Copy link
Contributor

Resolved by aspnet/Microsoft.Data.Sqlite#74

@bricelam bricelam added this to the 7.0.0-beta5 milestone Apr 28, 2015
@ajcvickers ajcvickers added the closed-fixed The issue has been fixed and is/will be included in the release indicated by the issue milestone. label Oct 15, 2022
@ajcvickers ajcvickers modified the milestones: 1.0.0-beta5, 1.0.0 Oct 15, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
closed-fixed The issue has been fixed and is/will be included in the release indicated by the issue milestone. type-bug
Projects
None yet
Development

No branches or pull requests

5 participants