• last updated 22 hours ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
merged changes from the oacs-5-9 branch and resolved conflicts

    • -16
    • +16
    ./oracle/upgrade/upgrade-4.7d6-5.0d1.sql
  1. … 7820 more files in changeset.
Allow copy of files/folders into the same folder of the original content. This is done by appending a numerical suffix to the name.

It required modifying copy stored procedures so they could accept a different name and title for the copy.

I have also removed redundant package definition in oracle code that was immediately overridden afterwards.

    • -0
    • +685
    ./oracle/upgrade/upgrade-5.9.1b4-5.9.1b5.sql
    • -0
    • +146
    ./postgresql/upgrade/upgrade-5.9.1b4-5.9.1b5.sql
  1. … 9 more files in changeset.
file upgrade-5.9.1b4-5.9.1b5.sql was initially added on branch oacs-5-9.

    • -0
    • +0
    ./oracle/upgrade/upgrade-5.9.1b4-5.9.1b5.sql
    • -0
    • +0
    ./postgresql/upgrade/upgrade-5.9.1b4-5.9.1b5.sql
Fix spelling errors

    • -16
    • +16
    ./oracle/upgrade/upgrade-4.7d6-5.0d1.sql
  1. … 35 more files in changeset.
Performance improvement in content_item__get_path stored procedure (thanks to Thomas Renner)

    • -0
    • +95
    ./postgresql/upgrade/upgrade-5.9.1b3-5.9.1b4.sql
  1. … 1 more file in changeset.
file upgrade-5.9.1b3-5.9.1b4.sql was initially added on branch oacs-5-9.

    • -0
    • +0
    ./postgresql/upgrade/upgrade-5.9.1b3-5.9.1b4.sql
fix issue #3303: wrong identifier due to different database structure in oracle

- Align type of parameter "storage_type" with type definition of cr_items.storage_type

- bump version to 5.9.1d27

    • -0
    • +213
    ./postgresql/upgrade/upgrade-5.9.1d26-5.9.1d27.sql
  1. … 1 more file in changeset.
file upgrade-5.9.1d26-5.9.1d27.sql was initially added on branch oacs-5-9.

    • -0
    • +0
    ./postgresql/upgrade/upgrade-5.9.1d26-5.9.1d27.sql
Improve documentation

    • -3
    • +2
    ./postgresql/upgrade/upgrade-5.9.1d25-5.9.1d26.sql
file upgrade-5.9.1d25-5.9.1d26.sql was initially added on branch oacs-5-9.

    • -0
    • +0
    ./postgresql/upgrade/upgrade-5.9.1d25-5.9.1d26.sql
- fix bug when updateing a user portrait, which was saved as "lob"

    • -0
    • +39
    ./postgresql/upgrade/upgrade-5.9.1d25-5.9.1d26.sql
  1. … 1 more file in changeset.
- make upgrade script more robust (when run twice)

    • -1
    • +1
    ./postgresql/upgrade/upgrade-5.9.1d22-5.9.1d23.sql
- fix cr_revision_latest_tr once more to reduce the number of dead tuples generated for xo* classes

- bump version number to 5.9.1d25

    • -0
    • +28
    ./postgresql/upgrade/upgrade-5.9.1d24-5.9.1d25.sql
  1. … 1 more file in changeset.
file upgrade-5.9.1d24-5.9.1d25.sql was initially added on branch oacs-5-9.

    • -0
    • +0
    ./postgresql/upgrade/upgrade-5.9.1d24-5.9.1d25.sql
- avoid call of deprecated sql variant with 12 args via API (many thnaks to Guenter Ernst)

- handling of NULL values in cr_revision_latest_tr (many thanks to Guenter Ernst)

- bump version to 5.9.1d24

    • -3
    • +3
    ./postgresql/upgrade/upgrade-5.9.1d22-5.9.1d23.sql
    • -0
    • +26
    ./postgresql/upgrade/upgrade-5.9.1d23-5.9.1d24.sql
  1. … 2 more files in changeset.
file upgrade-5.9.1d23-5.9.1d24.sql was initially added on branch oacs-5-9.

    • -0
    • +0
    ./postgresql/upgrade/upgrade-5.9.1d23-5.9.1d24.sql
Reduced generation of dead tuples in postgres.

Background: In the old version, the fields latest and live

revisions were updated always via two separate dmlDML statements.

Every update causes in PostgreSQL (tested to pg 9.6) one more dead

tuple, such that on busy systems, we see 30k + dead tuples per

hour. These dead tuples in turn cause more auto vacuum operations

and can lead to abandoned query plans.

This change can reduce the number of dead tuples on cr_items into

half, by allowing both fields to be set in one operation (namely

content_item__set_live_revision). This function has an optional 4th

argument that can cause this optimization. For legacy applications,

nothing changes.

Btw: since all commonly used applications use the live revision, the

fallback of the latest_revision is unused. One can consider to

remove the cr_revision_latest_tr, at least on on certain

installations.

bump revision to 5.1.9d23

    • -0
    • +90
    ./postgresql/upgrade/upgrade-5.9.1d22-5.9.1d23.sql
  1. … 1 more file in changeset.
file upgrade-5.9.1d22-5.9.1d23.sql was initially added on branch oacs-5-9.

    • -0
    • +0
    ./postgresql/upgrade/upgrade-5.9.1d22-5.9.1d23.sql
Fixed if statement in oracle upgrade script

Simplified upgrade-5.9.1d20-5.9.1d21.sql postgres script

    • -54
    • +30
    ./postgresql/upgrade/upgrade-5.9.1d20-5.9.1d21.sql
Added Oracle version of acs-cr upgrade-5.9.1d20-5.9.1d21.sql script and simplified postgres version.

file upgrade-5.9.1d20-5.9.1d21.sql was initially added on branch oacs-5-9.

    • -0
    • +0
    ./oracle/upgrade/upgrade-5.9.1d20-5.9.1d21.sql
Updated mimetypes

    • -0
    • +89
    ./postgresql/upgrade/upgrade-5.9.1d20-5.9.1d21.sql
  1. … 1 more file in changeset.
file upgrade-5.9.1d20-5.9.1d21.sql was initially added on branch oacs-5-9.

    • -0
    • +0
    ./postgresql/upgrade/upgrade-5.9.1d20-5.9.1d21.sql
- use same logic in all update-scripts for cr_mime_types

- update upgrade script to more powerful version used in later update scripts as well

    • -8
    • +24
    ./postgresql/upgrade/upgrade-5.9.1d11-5.9.1d12.sql
- fix old typo in label of unknown mimtype (was "Unkown")

    • -0
    • +1
    ./postgresql/upgrade/upgrade-5.9.1d19-5.9.1d20.sql
  1. … 1 more file in changeset.
file upgrade-5.9.1d19-5.9.1d20.sql was initially added on branch oacs-5-9.

    • -0
    • +0
    ./oracle/upgrade/upgrade-5.9.1d19-5.9.1d20.sql
    • -0
    • +0
    ./postgresql/upgrade/upgrade-5.9.1d19-5.9.1d20.sql
- use consistently varchar(1000) for object_types

- bump version number to 5.9.1d19

    • -0
    • +33
    ./postgresql/upgrade/upgrade-5.9.1d18-5.9.1d19.sql
  1. … 1 more file in changeset.