[schemaserial] mitigate critical message during migration
authorAurelien Campeas <aurelien.campeas@logilab.fr>
Fri, 03 May 2013 17:26:23 +0200
changeset 8986 f094b72d3a6c
parent 8985 be04a3e01ac9
child 8988 6cd912702239
[schemaserial] mitigate critical message during migration We can't fetch extra_props because it is not yet there.
server/schemaserial.py
--- a/server/schemaserial.py	Wed May 22 06:30:16 2013 +0200
+++ b/server/schemaserial.py	Fri May 03 17:26:23 2013 +0200
@@ -202,6 +202,8 @@
         extra_props = dict(session.execute('Any X, XTP WHERE X is CWAttribute, '
                                            'X extra_props XTP'))
     except Exception:
+        session.critical('Previous CRITICAL notification about extra_props is not '
+                         'a problem if you are migrating to cubicweb 3.17')
         extra_props = {} # not yet in the schema (introduced by 3.17 migration)
     for values in session.execute(
         'Any X,SE,RT,OE,CARD,ORD,DESC,IDX,FTIDX,I18N,DFLT WHERE X is CWAttribute,'