• last updated 16 hours ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Implemented a safe way to delete constraints, as these constraints didn't exist. It's most likely got to do with the PG upgrade from 7.2 to 7.3 not recording constraints properly. This is a workaround, not a fix. See bug #1294.

    • -2
    • +30
    ./postgresql/upgrade/upgrade-5.0.0a5-5.0.0a6.sql
Untabify

delete--> del upgrade

    • -0
    • +404
    ./oracle/upgrade/upgrade-4.6.4-5.0d1.sql
fix inconsistency between notifications-replies-extra-create and upgrade scripts, hopefully this finally fixed 1231

    • -1
    • +1
    ./oracle/notifications-replies-extra-create.sql
    • -1
    • +1
    ./oracle/upgrade/upgrade-4.6.4-5.0d1.sql
no need to drop table if you are just changing a constraint.

    • -42
    • +11
    ./postgresql/upgrade/upgrade-5.0.0a5-5.0.0a6.sql
the upgrade failed because notification_user_map constraint notif_user_map_notif_id_fk needed the pk on notifications_bak, now drops it and recreates it after the table is reloaded

use clobs for to_addr, headers, body; fix load_qmail_mail_queue.holdinsert query, fix upgrade script, make constriant names conform to standards. Fixes bug 1231

    • -5
    • +6
    ./oracle/upgrade/upgrade-4.6.4-5.0d1.sql
    • -2
    • +3
    ./postgresql/notifications-replies-extra-create.sql
  1. … 2 more files in changeset.
text datatype should be clob for oracle

    • -5
    • +6
    ./oracle/notifications-replies-extra-create.sql
making notifications cascade when acs objects are deleted, see bug 260

    • -2
    • +3
    ./oracle/notifications-core-create.sql
    • -2
    • +3
    ./postgresql/notifications-core-create.sql
    • -0
    • +42
    ./postgresql/upgrade/upgrade-5.0.0a5-5.0.0a6.sql