• last updated 11 hours ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
More function_args cleanup

- removed one more definition referring to a deleted function

- make sure we always get argument names via PostgreSQL

- aligned argument names with stubs (apm__set_value and apm__get_value)

- bumped version number to 5.10.1b7

    • -505
    • +500
    ./postgresql/apm-create.sql
    • -0
    • +12
    ./postgresql/upgrade/upgrade-5.10.1b6-5.10.1b7.sql
  1. … 1 more file in changeset.
file upgrade-5.10.1b6-5.10.1b7.sql was initially added on branch oacs-5-10.

    • -0
    • +0
    ./postgresql/upgrade/upgrade-5.10.1b6-5.10.1b7.sql
Various fixes for "function_args"

- The default value for "authority_id" in acs_user__new was missing.

- Removed leftovers from earlier changes in the SQL API. The update

scripts did not care about function args, so orphaned entries could

cause confusions.

- The drop-package SQL function did not care about deleting entries on

the function args table. The function args deleted here are created

automatically by the Tcl proc "package_generate_body".

- bumped verison of acs-kernel to 5.10.1b6

    • -8
    • +2
    ./postgresql/community-core-create.sql
    • -0
    • +54
    ./postgresql/upgrade/upgrade-5.10.1b5-5.10.1b6.sql
  1. … 1 more file in changeset.
file upgrade-5.10.1b5-5.10.1b6.sql was initially added on branch oacs-5-10.

    • -0
    • +0
    ./postgresql/upgrade/upgrade-5.10.1b5-5.10.1b6.sql
Fixed issue introduced in OpenACS 5.9.0

The old version did not insert a property value via the

sec_session_property__upsert() in PostgreSQL on the initial setting

(later updates were OK). The broken version was just adding a tuple

and left the "property_value" empty.

Many thanks to Jonathan Kelley for identifying the issue and reporting it.

    • -16
    • +16
    ./postgresql/security-create.sql
    • -0
    • +37
    ./postgresql/upgrade/upgrade-5.10.1b4-5.10.1b5.sql
  1. … 1 more file in changeset.
file upgrade-5.10.1b4-5.10.1b5.sql was initially added on branch oacs-5-10.

    • -0
    • +0
    ./postgresql/upgrade/upgrade-5.10.1b4-5.10.1b5.sql
Silence potentially confusing warning during first installation

    • -5
    • +5
    ./postgresql/acs-permissions-create.sql
Small update for cluster support

- Improved visualization of cluster nodes that we lost contact to

- New kernel parameters to reduce hard-coded values and to make purpose more explicit

* new parameter ClusterHeartbeatInterval (default 20s),

was hardcoded before to the new default value

* renamed PreferredLocationRegexp -> ClusterPreferredLocationRegexp

* renamed EnableLoggingP -> ClusterEnableLoggingP

- Bumped version numbers:

* acs-kernel to 5.10.1b3

* acs-tcl to 5.10.1b2

* acs-admin to 5.10.1b2

acs-kernel acs-admin acs-tcl/

    • -0
    • +24
    ./postgresql/upgrade/upgrade-5.10.1b2-5.10.1b3.sql
  1. … 6 more files in changeset.
file upgrade-5.10.1b2-5.10.1b3.sql was initially added on branch oacs-5-10.

    • -0
    • +0
    ./oracle/upgrade/upgrade-5.10.1b2-5.10.1b3.sql
    • -0
    • +0
    ./postgresql/upgrade/upgrade-5.10.1b2-5.10.1b3.sql
fixed typo

    • -2
    • +2
    ./postgresql/acs-permissions-create.sql
    • -3
    • +3
    ./postgresql/rel-constraints-body-create.sql
  1. … 2 more files in changeset.
file upgrade-5.10.1d10-5.18.1d19.sql was initially added on branch oacs-5-10.

    • -0
    • +0
    ./oracle/upgrade/upgrade-5.10.1d10-5.18.1d19.sql
file upgrade-5.10.1d18-5.10.1d19.sql was initially added on branch oacs-5-10.

    • -0
    • +0
    ./postgresql/upgrade/upgrade-5.10.1d18-5.10.1d19.sql
made names of SQL functions explicit to ease calling directly from the Tcl level

    • -0
    • +680
    ./oracle/upgrade/upgrade-5.10.1d10-5.18.1d19.sql
    • -0
    • +53
    ./postgresql/upgrade/upgrade-5.10.1d18-5.10.1d19.sql
  1. … 1 more file in changeset.
Remove no_alarms_until column

Rationale: the column or the related api is never used in upstream code to check whether notifications should be sent or not or not. The UI to manage the column's value was not linked anywhere. On the instances accessible by me downstream, no tuple was found where this column had a value.

    • -0
    • +200
    ./oracle/upgrade/upgrade-5.10.1d17-5.10.1d18.sql
    • -37
    • +1
    ./postgresql/community-core-create.sql
    • -0
    • +49
    ./postgresql/upgrade/upgrade-5.10.1d17-5.10.1d18.sql
  1. … 14 more files in changeset.
file upgrade-5.10.1d17-5.10.1d18.sql was initially added on branch oacs-5-10.

    • -0
    • +0
    ./oracle/upgrade/upgrade-5.10.1d17-5.10.1d18.sql
    • -0
    • +0
    ./postgresql/upgrade/upgrade-5.10.1d17-5.10.1d18.sql
Added proc "membership_rel::expire" so that all membership states are now covered. Note: The Oracle part is best effort only!

    • -0
    • +249
    ./oracle/upgrade/upgrade-5.10.1d16-5.10.1d17.sql
    • -1
    • +25
    ./postgresql/groups-body-create.sql
    • -0
    • +22
    ./postgresql/upgrade/upgrade-5.10.1d16-5.10.1d17.sql
  1. … 6 more files in changeset.
file upgrade-5.10.1d16-5.10.1d17.sql was initially added on branch oacs-5-10.

    • -0
    • +0
    ./oracle/upgrade/upgrade-5.10.1d16-5.10.1d17.sql
    • -0
    • +0
    ./postgresql/upgrade/upgrade-5.10.1d16-5.10.1d17.sql
new partial index for a common query

... checking for "approved" members

    • -0
    • +5
    ./postgresql/upgrade/upgrade-5.10.1d13-5.10.1d14.sql
  1. … 1 more file in changeset.
file upgrade-5.10.1d13-5.10.1d14.sql was initially added on branch oacs-5-10.

    • -0
    • +0
    ./postgresql/upgrade/upgrade-5.10.1d13-5.10.1d14.sql
make update script more robust in case the table acs_privilege_descendant_map was already dropped

The old version worked on pg14, but as it looks, not on earlier pg versions.

    • -1
    • +22
    ./postgresql/upgrade/upgrade-5.10.1d11-5.10.1d12.sql
Cleanup leftover util user messages, that we won't persist anymore

    • -0
    • +6
    ./postgresql/upgrade/upgrade-5.10.1d12-5.10.1d13.sql
  1. … 1 more file in changeset.
file upgrade-5.10.1d12-5.10.1d13.sql was initially added on branch oacs-5-10.

    • -0
    • +0
    ./postgresql/upgrade/upgrade-5.10.1d12-5.10.1d13.sql
Cleanup of acs_object_context_index' and friends in creation scripts

This change completes the commit [1] from 2019, where the cleanup was performed

acs_object_context_index and its maintenance functions just as an update script.

This change addresses this also in the creation scripts and in packages, still

depending on the old functions.

[1] https://fisheye.openacs.org/changelog/OpenACS?cs=oacs-5-10%3Ahectorr%3A20190708160122

    • -308
    • +1
    ./postgresql/acs-objects-create.sql
    • -250
    • +42
    ./postgresql/acs-permissions-create.sql
    • -0
    • +57
    ./postgresql/upgrade/upgrade-5.10.1d11-5.10.1d12.sql
  1. … 5 more files in changeset.
file upgrade-5.10.1d11-5.10.1d12.sql was initially added on branch oacs-5-10.

    • -0
    • +0
    ./postgresql/upgrade/upgrade-5.10.1d11-5.10.1d12.sql
file upgrade-5.10.1d9-5.10.1d10.sql was initially added on branch oacs-5-10.

    • -0
    • +0
    ./postgresql/upgrade/upgrade-5.10.1d9-5.10.1d10.sql
Adjust legacy data types of acs_object_types.object_type and acs_objects.object_type

This change addresses the problem mentioned in

https://cvs.openacs.org/changelog/OpenACS?cs=oacs-5-10%3Agustafn%3A20220729185340

https://github.com/openacs/openacs-core/commit/be44691f06627678122bd913bc3c95c80e93f403

which happens in some legacy applications (such as

e.g. openacs.org) where the data types of the following two

attributes are different.

acs_object_types.object_type

acs_objects.object_type

On new installations (at least concerning the last 10 years) these

data types are the same. So, probably an update script was missing

ages ago.

Since this change affects the basic object structure, MANY views

depend on this datatype and have to be dropped and recreate to

allow the correction of the datatype.

Therefore, we do not want to run this script on all sites, but

only on those where it is necessary.

    • -0
    • +340
    ./postgresql/upgrade/upgrade-5.10.1d9-5.10.1d10.sql
  1. … 1 more file in changeset.
Added membership "expired" to membership states. "expired" can be

used for "dormant" accounts, which are neither "banned" nor "deleted".

    • -0
    • +9
    ./postgresql/upgrade/upgrade-5.10.1d8-5.10.1d9.sql
  1. … 1 more file in changeset.
file upgrade-5.10.1d8-5.10.1d9.sql was initially added on branch oacs-5-10.

    • -0
    • +0
    ./oracle/upgrade/upgrade-5.10.1d8-5.10.1d9.sql
    • -0
    • +0
    ./postgresql/upgrade/upgrade-5.10.1d8-5.10.1d9.sql
Improve robustness of upgrade script for legacy applications

In case, an installation has the legacy view (must be from very old installations)

in place, it is necessary to drop it before registered_users, otherwise

PostgreSQL will complain that it cannot drop view registered_users because

other objects depend on it.

Many thanks to Franz Penz to report this potential problem for old sites.

Align names used in utility db functions in Oracle and PostgreSQL

Over the years, the names used in the function for PostgreSQL and

Oracle drifted away, which is a problem when using call-by-name

convention for stored procedures. Furthermore, recent Oracle versions

do not allow attributes named "table" (for table_name). So the longer

version is now used uniformily. Fortunately, nsf allow abbreviation

for named parameters (like Tcl does), such one can use both

"-table_name" and "-table".

Bumped version number to 5.10.1d7.

    • -0
    • +312
    ./oracle/upgrade/upgrade-5.10.1d6-5.10.1d7.sql
    • -158
    • +157
    ./postgresql/utilities-create.sql
    • -0
    • +167
    ./postgresql/upgrade/upgrade-5.10.1d6-5.10.1d7.sql
  1. … 1 more file in changeset.