• last updated 1 hour ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
file upgrade-5.8.1d2-5.8.1d3.sql was initially added on branch oacs-5-8.

    • -0
    • +0
    ./upgrade-5.8.1d2-5.8.1d3.sql
- fix bug #3064

  1. … 1 more file in changeset.
file upgrade-5.8.1d1-5.8.1d2.sql was initially added on branch oacs-5-8.

    • -0
    • +0
    ./upgrade-5.8.1d1-5.8.1d2.sql
for some reason function apm__register_parameter/10 was missing on openacs.org.

    • -0
    • +74
    ./upgrade-5.8.0d4-5.8.0d5.sql
  1. … 1 more file in changeset.
on pg version 9.0 ( and lower ) the function string_to_array takes only two parameters.

  1. … 1 more file in changeset.
Creating recursive version of permissions functions iff pg version is >= 8.4.

    • -104
    • +161
    ./upgrade-5.8.0d3-5.8.0d4.sql
  1. … 3 more files in changeset.
Renaming parameters used on recursive query in order to avoid name clashing with function parameters ( seems to happen just in pg 8.4 ).

  1. … 1 more file in changeset.
Rewriting acs_permission__permission_p function to use recursive queries ( available in PG since 8.4 ) and modifiying

queries around core packages to avoid checking persmissions using a subquery on the acs_object_party_privilege_map view.

    • -0
    • +116
    ./upgrade-5.8.0d3-5.8.0d4.sql
  1. … 14 more files in changeset.
- fixed bug (backport of fix in rev 1.74 of postgresql/apm-create.sql)

- bump version number to 5.6.1

  1. … 2 more files in changeset.
file upgrade-5.6.0-5.6.1.sql was initially added on branch oacs-5-6.

    • -0
    • +0
    ./upgrade-5.6.0-5.6.1.sql
Some time ago some plpgsql functions were changed in order to be compatible with pg 8.x, create scripts were modified but upgrade scripts were missing ( at least i couldn't find them) http://fisheye.openacs.org/changelog/OpenACS?cs=MAIN%3Ajeffd%3A20090210183154 . Bumping up package versions accordingly.

    • -0
    • +77
    ./upgrade-5.8.0d2-5.8.0d3.sql
  1. … 7 more files in changeset.
Upgrade scripts contain the following changes:

- getting right name of triggers, following the pattern *_tr

- redefining funtion arguments for each function using define_function_args

- getting rid of unncesary backslashes, used for escaping, in some functions.

- redefinitions of content_type__refresh_trigger and content_type__drop_type in order to get rid of some 7.2 vs 7.3 querying.

    • -0
    • +310
    ./upgrade-5.8.0d1-5.8.0d2.sql
  1. … 3 more files in changeset.
    • -197
    • +0
    ./upgrade-5.7.0d9-upgrade-5.7.0d10.sql
  1. … 1 more file in changeset.
Removing wrongly named upgrade script. Otherwise it appears at the top of the list for scripts to be ran when upgrading. Content is included on upgrade script upgrade-5.7.0d10-5.7.0d11.sql anyway.

    • -197
    • +0
    ./upgrade-5.7.0d9-upgrade-5.7.0d10.sql
file upgrade-5.7.0d10-5.7.0d11.sql was added on branch oacs-5-7 on 2011-05-30 08:51:16 +0000

- Added comments to function arguments 'create_table_p' and 'dynamic_p'

- Update script for 5.7.0d10 was called

postgresql/upgrade/upgrade-5.7.0d9-upgrade-5.7.0d10.sql

instead of

postgresql/upgrade/upgrade-5.7.0d9-5.7.0d10.sql

so it was never executed. Added the content of d9-d10 to d10-d11.

    • -0
    • +297
    ./upgrade-5.7.0d10-5.7.0d11.sql
  1. … 2 more files in changeset.
1. Added "--default foo" style comments to new PL/pgSQL function parameters

because xotcl-core, rather than use the metadata created by define_function_params,

ASSIGNS SEMANTICS TO THESE SQL COMMENTS. Bah. If I truly cared about quality

I'd insist the xotcl people fix their code and do things right, but I know that

would never happen so ... kludge away.

2. xotcl-core adds CR attributes (rather than fix core). So my fixing of

core conflicts, meaning I have to kludge again. Still needs to be fixed

for oracle.

    • -0
    • +197
    ./upgrade-5.7.0d9-upgrade-5.7.0d10.sql
  1. … 3 more files in changeset.
Added upgrade script to redefine a couple of plpgsql functions that fail with

later versions of PG due to tighter type checking.

    • -0
    • +78
    ./upgrade-5.7.0d8-5.7.0d9.sql
  1. … 1 more file in changeset.
Fixing many bugs

    • -0
    • +191
    ./upgrade-5.7.0d7-5.7.0d8.sql
    • -67
    • +0
    ./upgrade-5.7.0d7-upgrade-5.7.0d8.sql
  1. … 1 more file in changeset.
Had to remove the cascade_p feature of the new drop_type procedure, because

implementing it in Oracle would require a huge reorganization of the order

of definition of object and metadata tables and their associated tables,

which just is not going to happen.

    • -0
    • +67
    ./upgrade-5.7.0d7-upgrade-5.7.0d8.sql
  1. … 2 more files in changeset.
*** empty log message ***

  1. … 1 more file in changeset.
Further bug fixing ... hopefully, testing with AOM will tell the tale.

Also bumped *info file.

  1. … 2 more files in changeset.
Fixed a bug with the new version of create_type, found as I was porting to

Oracle (there *is* a use for Oracle, I'll be damned!).

    • -0
    • +117
    ./upgrade-5.7.0d5-5.7.0d6.sql
  1. … 1 more file in changeset.
Believe it or not, "create_type" has never, ever checked to see if the

given supertype is a valid type. The code now verifies that the given

supertype is a child of "acs_object", except when supertype is passed in

as NULL or '' (in which case it's set to acs_object). Only did it for

PostgreSQL since it's been around forever and whatever Oracle users don't

know, won't hurt them.

    • -0
    • +119
    ./upgrade-5.7.0d4-5.6.0d5.sql
  1. … 2 more files in changeset.
Moved table building and column adding code from content repository to

kernel, so all objects can benefit. Part of the acs object management package

work.

  1. … 5 more files in changeset.
Upgrade scripts for changes on object metadata creation (adding automatic

table and column creation to base objects as well as CR object, object views,

etc).

    • -0
    • +936
    ./upgrade-5.7.0d3-5.7.0d4.sql
  1. … 3 more files in changeset.
On my previous commit I added a not null constraint for name column on site_nodes, the problem is that main site node on oracle has a NULL name ( given the fact that empty strings are managed as NULL on Oracle ) therefore doesnt make sense to have such constraint.

  1. … 3 more files in changeset.
- Avoiding usage of coalesce function on site_nodes table columns in WHERE clause, this was leading to usage of sequencial scans which can be expensive when having a huge amount of site_nodes. Instead we go for isolation of the case when requestion a node with a null parent ( this would be the main site node ) and we use the = operator so the planner goes for a index scan.

- Adding not null constraint to site_nodes(name)

    • -0
    • +82
    ./upgrade-5.7.0d2-5.7.0d3.sql
  1. … 4 more files in changeset.
Merged oacs-5-6 to HEAD. HEAD now installs and passes all core tests. There

may still be some lingering problems due to my screwing up the oacs-5-6

branch earlier, I'll be looking into this later.

  1. … 212 more files in changeset.
Changes for supporting postgresql 9.0:

- Avoiding usage of SQL reserved keywords on plpsql functions (plpsql lexer and parser were reworked).

- Fixing all those places on which FROM clause was automatically added by PG ( PG Config add_missing_from parameter was removed for this release of PG ).

Many thanks to Tracy Adams and Jeff Lu for providing first version of the patches.

    • -0
    • +103
    ./upgrade-5.7.0d1-5.7.0d2.sql
  1. … 16 more files in changeset.