Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
sqlite3.InterfaceError: Error binding parameter 1 - probably unsupported type.
See original GitHub issueEncountered this error during a write to the database using the library.
The objects being written were collections.Counter[Tuple[str]] and Dict[str, Counter[Tuple[str]]]
Both types of objects previously worked fine in being written to the DB, but this time, it threw an error. Not sure why, and I haven’t been able to narrow it down any further, but it did corrupt my existing DB that was being built over a long process with successive (batched) write operations.
sqlite3.InterfaceError: Error binding parameter 1 - probably unsupported type.
Issue Analytics
- State:
- Created a year ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Thanks for the additional info. If the error is not deterministic, this will be a tricky. I’ll try to google around.
-1 on bypassing DB errors by copying the DB… who knows what else is wrong, plus such copying can be done at the application level, like you said.
Is there a way to find out what object, if at all, when being committed, caused an error in sqlite3? That would give us a hint about the point of failure. I don’t mean the top-level object, I mean the specific value. Maybe this can be phrased better, I’m unfortunately not too familiar with sqlite3. Thanks!