[migration] don't handle data deletion anymore on schema changes In most cases when we want to drop some entity/relation type, we don't care whether hooks are called on their deletion. There is even low chances that some hooks still exists, based on an old version of the schema. Last but not least, this is horribly inefficient. So this should be clearly documented and handled by application's programmer if desired. This patch removes unnecessary deletion (because table or column will be later dropped) and reimplements the case of partial deletion (only one relation definition among several, hence the database structure isn't modified) using sql. Only one test regarding deletion of inlined relation def is added as other cases seem to be covered by existing tests. Closes #7023315

     1

/* styles for input with suggestions (as for tags and keywords)

     2

 *

     3

 *  :organization: Logilab

     4

 *  :copyright: 2003-2010 LOGILAB S.A. (Paris, FRANCE), all rights reserved.

     5

 *  :contact: http://www.logilab.fr/ -- mailto:contact@logilab.fr

     6

 */

     7

     8

div.sgform div.combobox {

     9

  z-index: 300;

    10

  margin-left: 3px;

    11

  width: 150px;

    12

}

    13

    14

div.sgform div.combobox input.suggestions {

    15

  width: 100%;

    16

}

    17

    18

div.sgform  select{

    19

  width: 155px;

    20

}

    21

    22

div.sgformbuttons {

    23

  margin-left: 3px;

    24

}

    25

    26

div.sgformbuttons a {

    27

  font-weight: bold;

    28

  padding:2px 0px;

    29

}

    30

    31

a.sglink {

    32

  color: #000;

    33

  font-weight: bold;

    34

  display: block;

    35

  background: url("puce.png") 98% 5px no-repeat;

    36

  margin-left: 3px;

    37

  padding: 2px 16px 2px 0px;

    38

}

    39

    40

div.suggholder {

    41

  z-index: 300;

    42

  position: absolute;

    43

}