-
-
Notifications
You must be signed in to change notification settings - Fork 111
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
Only set .last_rowid and .last_pk for single update/inserts, not for .insert_all()/.upsert_all() with multiple records #98
Comments
Investigate this traceback:
|
I need a test that reproduces this. |
I have a hunch that the root of the problem here is that accessing sqlite-utils/sqlite_utils/db.py Lines 1102 to 1113 in 6161ebf
In the bug I'm seeing (which I still haven't reduced to a reproducible test) the debugger shows me this at that point:
But here's the weird thing... there's no row in the table with a rowid of 100!
So what the heck is going on? The last SQL statement I executed here was an
So where did that |
Why do I even care about I'm trying to ensure that after you insert or upsert a row you can use So maybe it doesn't make sense to make The documentation doesn't say it should work for sqlite-utils/sqlite_utils/db.py Lines 1113 to 1124 in 6161ebf
|
In mucking around with
|
Implementation plan: |
Hi @simonw - wondering if you might be able to shed some light here. I've seemed to reproduce this issue.
Interesting enough, I found that omitting the Let me know how I can help out! |
No description provided.
The text was updated successfully, but these errors were encountered: