#12612: SQLite3 executemany() exception handling is too broad
---------------------------------------------------+------------------------
Reporter: Niels <[email protected]> | Owner:
gabrielhurley
Status: assigned | Milestone: 1.2
Component: Database layer (models, ORM) | Version: 1.2-alpha
Resolution: | Keywords:
sqlite,sqlite3
Stage: Accepted | Has_patch: 1
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
---------------------------------------------------+------------------------
Changes (by gabrielhurley):
* owner: nobody => gabrielhurley
* status: new => assigned
* has_patch: 0 => 1
Comment:
This was introduced in @6218 as the solution to #4765. I agree with Niels
that the solution in that patch (suppressing an error regarding a
malformed query and returning None) is not the right direction.
I can't find any discussion of why that decision was made, and there are
no tests for executemany() anywhere that I see.
I'm adding a patch which lets the error bubble up and adds tests to check
for the behaviors noted in this ticket and #4896.
--
Ticket URL: <http://code.djangoproject.com/ticket/12612#comment:3>
Django <http://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
