-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
"no such table" error #223
Comments
Because connection doesn't have exclusion. |
dup #216 |
Hi, sorry, either I'm misunderstanding or I wasn't clear in the description. This is about our own testcase of an application built on go-sqlite3, not the go-sqlite3 testcaess. In our application testcase, the db is opened with the _txlock=exclusive option. It mostly runs correctly, but with a very massive concurrent testcase I got this case where my db query claimed that a table didn't exist. |
@hallyn Have you found the root cause of this issue? I'm facing a pretty similar error; the table should have been create, with lots of queries been executed successfully, but later an error was thrown claiming |
@Higan Do you have an example of your code that is having a problem? Are you using an actual database file, or an in-memory database? Are you using any temporary tables? |
Maybe this would help someone I had the same issue with 'no such table' and found an exact explanation: If sql.Rows is not closed before next query then driver returns no such table on next query. Issue exists only for in-memory storage, same test for file backed db runs fine. After that, I found the part of code where I had forgotten to do rows.Close(), fixed that and now it works with no issues. |
setup: Ubuntu 20.04.1 LTS database:
stdout: |
@mattn |
@mrbardia72 Please open a new issue, with sufficient detail to diagnose your error. |
@mattn add table users, try this |
Hi,
when doing some heavy stress-testing of our application which imports go-sqlite3, during one failure case I saw:
error: no such table: containers
This was in the middle of a run, sandwiched between many successful queries and actions on the containers table.
This was on a brand new built vm, using go-sqlite commit b4142c4.
Do you have any particular suggestions for figuring out what may have gone wrong?
Thanks!
The text was updated successfully, but these errors were encountered: