#30073 closed Bug (duplicate)
SQLite 3.26.0 breaks the tests running using in-memory database
| Reported by: | Faran Negarestan | Owned by: | nobody |
|---|---|---|---|
| Component: | Database layer (models, ORM) | Version: | 2.1 |
| Severity: | Normal | Keywords: | |
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
I'm on MacOS Mojave, sqlite 3.26.0 installed using brew and python 3.6.5 and Django 2.1.1.
Since the last sqlite3 update I get the following error while running tests:
sqlite3.OperationalError: no such table: main.flipr_userold
Where flipr_user is my table. I didn't use to get this error and under Linux it still runs without any problem. I suspect very much that it's caused by sqlite3 but would love to know if it is observed by other user as well.
Change History (3)
comment:1 by , 5 years ago
| Summary: | Latest version of sqlite break the tests running using in-memory database → Latest version of sqlite breaks the tests running using in-memory database |
|---|
comment:2 by , 5 years ago
| Resolution: | → duplicate |
|---|---|
| Status: | new → closed |
comment:3 by , 5 years ago
| Summary: | Latest version of sqlite breaks the tests running using in-memory database → SQLite 3.26.0 breaks the tests running using in-memory database |
|---|
Note:
See TracTickets
for help on using tickets.
Duplicate of #29182, #30016 which will be fixed in Django 2.1.5 which should be released tomorrow.