# HG changeset patch
# User Sylvain Thénault <sylvain.thenault@logilab.fr>
# Date 1478626667 -3600
# Node ID 4a387179fa337b174ecec613a84a68a95c2515e5
# Parent  9d478b81f6d7b74d882c769b22788f3d8c6f4e3e
[migration] Drop cw_schema relation first

without this, we ends up with the traceback shown at
https://www.cubicweb.org/ticket/16130960. This is not the proper fix, which
I have not been able to find. It seems due to this very rare case of deletion
of such relation linked to CWRType vs order of execution of operation (in this
case, the operation deleting the entity table is run before some other queries
using it).

As forcing this relation to be deleted before the entity type fixes the problem
while this case seems rare enough, IMO this patch is "good enough".

Closes #16130960

diff -r 9d478b81f6d7 -r 4a387179fa33 cubicweb/misc/migration/3.24.0_Any.py
--- a/cubicweb/misc/migration/3.24.0_Any.py	Tue Nov 08 18:34:22 2016 +0100
+++ b/cubicweb/misc/migration/3.24.0_Any.py	Tue Nov 08 18:37:47 2016 +0100
@@ -8,4 +8,6 @@
 sql('ALTER TABLE entities DROP COLUMN extid')
 sql('DROP INDEX entities_type_idx')
 
+# force cw_schema deletion before CWSourceSchemaConfig to avoid nasty bug
+drop_relation_type('cw_schema')
 drop_entity_type('CWSourceSchemaConfig')