[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

/*!

     2

 * FullCalendar v1.6.4 Print Stylesheet

     3

 * Docs & License: http://arshaw.com/fullcalendar/

     4

 * (c) 2013 Adam Shaw

     5

 */

     6

     7

/*

     8

 * Include this stylesheet on your page to get a more printer-friendly calendar.

     9

 * When including this stylesheet, use the media='print' attribute of the <link> tag.

    10

 * Make sure to include this stylesheet IN ADDITION to the regular fullcalendar.css.

    11

 */

    12

    13

    14

 /* Events

    15

-----------------------------------------------------*/

    16

    17

.fc-event {

    18

	background: #fff !important;

    19

	color: #000 !important;

    20

	}

    21

    22

/* for vertical events */

    23

    24

.fc-event-bg {

    25

	display: none !important;

    26

	}

    27

    28

.fc-event .ui-resizable-handle {

    29

	display: none !important;

    30

	}

    31

    32