#19351 closed Bug (fixed)
Two SQLite issues with bulk_insert
Reported by: | Anssi Kääriäinen | Owned by: | Anssi Kääriäinen |
---|---|---|---|
Component: | Database layer (models, ORM) | Version: | 1.4 |
Severity: | Normal | Keywords: | sqlite bulk_insert |
Cc: | Triage Stage: | Accepted | |
Has patch: | yes | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description
SQLite + bulk_insert has two issues:
- If you insert objects with same values for all fields the objects will be collapsed.
- If you insert more than 500 objects and the objects have just a single field a SQLite limit will be hit.
The first issue is technically a data-loss issue. However it isn't likely to be hit - it means you are inserting exactly similar objects in a same batch, and that isn't likely. A backpatch to 1.4 seems to be in place as the fix is trivial: use UNION ALL instead of UNION when constructing the insert query.
Change History (5)
comment:1 by , 12 years ago
comment:2 by , 12 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
In a27582484cf814554907d2d1ad077852de36963f: