#30033: SQLite schema editor should use the documented process to emulate table
alterations on SQlite3.
-------------------------------------+-------------------------------------
     Reporter:  Simon Charette       |                    Owner:  Simon
         Type:                       |  Charette
  Cleanup/optimization               |                   Status:  new
    Component:  Migrations           |                  Version:  master
     Severity:  Release blocker      |               Resolution:
     Keywords:                       |             Triage Stage:  Accepted
    Has patch:  0                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  0
Easy pickings:  0                    |                    UI/UX:  0
-------------------------------------+-------------------------------------
Changes (by Tim Graham):

 * status:  closed => new
 * has_patch:  1 => 0
 * resolution:  fixed =>
 * severity:  Normal => Release blocker
 * stage:  Ready for checkin => Accepted


Comment:

 On Ubuntu 16.04 which has SQLite 3.11, some problems appeared after
 7289874adceec46b5367ec3157cdd10c711253a0:
 {{{
 ======================================================================
 ERROR: test_m2m_rename_field_in_target_model (schema.tests.SchemaTests)
 ----------------------------------------------------------------------
 Traceback (most recent call last):
   File "/media/sf_django/django/db/backends/utils.py", line 82, in
 _execute
     return self.cursor.execute(sql)
   File "/media/sf_django/django/db/backends/sqlite3/base.py", line 360, in
 execute
     return Database.Cursor.execute(self, query)
 sqlite3.OperationalError: no such table: schema_tagm2mtest

 The above exception was the direct cause of the following exception:

 Traceback (most recent call last):
   File "/media/sf_django/tests/schema/tests.py", line 70, in tearDown
     self.delete_tables()
   File "/media/sf_django/tests/schema/tests.py", line 97, in delete_tables
     connection.enable_constraint_checking()
   File "/media/sf_django/django/db/backends/sqlite3/schema.py", line 34,
 in __exit__
     self.connection.check_constraints()
   File "/media/sf_django/django/db/backends/sqlite3/base.py", line 320, in
 check_constraints
     column_name, referenced_column_name,
   File "/media/sf_django/django/db/backends/utils.py", line 67, in execute
     return self._execute_with_wrappers(sql, params, many=False,
 executor=self._execute)
   File "/media/sf_django/django/db/backends/utils.py", line 76, in
 _execute_with_wrappers
     return executor(sql, params, many, context)
   File "/media/sf_django/django/db/backends/utils.py", line 84, in
 _execute
     return self.cursor.execute(sql, params)
   File "/media/sf_django/django/db/utils.py", line 89, in __exit__
     raise dj_exc_value.with_traceback(traceback) from exc_value
   File "/media/sf_django/django/db/backends/utils.py", line 82, in
 _execute
     return self.cursor.execute(sql)
   File "/media/sf_django/django/db/backends/sqlite3/base.py", line 360, in
 execute
     return Database.Cursor.execute(self, query)
 django.db.utils.OperationalError: no such table: schema_tagm2mtest
 }}}

-- 
Ticket URL: <https://code.djangoproject.com/ticket/30033#comment:8>
Django <https://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 unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.bb7554c86af2e931d07445b87e0b6f7a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to