• last updated 20 hours ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
This old version of the view update is superseeded by upgrade-5.3.0d1, apart from the fact that on none of my sites moving from pre 5.2 it has been working on an upgrade (usually fails due to image content type)

    • -26
    • +1
    ./postgresql/upgrade/upgrade-5.2.1d1-5.2.1d2.sql
Move content_revision__new functions to a seperate upgrade script that

will run after beta2.

    • -281
    • +1
    ./postgresql/upgrade/upgrade-5.3.0b1-5.3.0b2.sql
    • -0
    • +288
    ./postgresql/upgrade/upgrade-5.3.0b2-5.3.0b3.sql
Recreate all content_revision__new functions.

    • -2
    • +282
    ./postgresql/upgrade/upgrade-5.3.0b1-5.3.0b2.sql
Recreating the trigger without recreating the view can cause a problem

in a very specific case. It doesn't hurt to recreate the view (which

calls refresh_trigger)

Fix upgrade script to update the correct revision_id for the template

since template_id is a cr_items.item_id.

Update default template to use text instead of content tag to property grab

text from filesystem stored revisions.

Add Open Documents MIME types

    • -0
    • +54
    ./postgresql/upgrade/upgrade-5.3.0d7-5.3.0d8.sql
Fixed an upgrade ordering problem

    • -10
    • +0
    ./oracle/upgrade/upgrade-5.1.0-5.1.1.sql
Fixed an upgrade script ordering issue

    • -0
    • +50
    ./postgresql/upgrade/upgrade-5.2.0d18-5.2.0d19.sql