• last updated 16 hours ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
- update postgres function to modern style plpgsql definitions using dollar quoting

    • -102
    • +120
    ./test/rel-constraints-test.sql
    • -56
    • +92
    ./test/rel-segments-test-types-create.sql
    • -134
    • +159
    ./test/rel-segments-test.sql
  1. … 1 more file in changeset.
- fixed bug (backport of fix in rev 1.74 of postgresql/apm-create.sql)

- bump version number to 5.6.1

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

    • -0
    • +0
    ./postgresql/upgrade/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
    ./postgresql/upgrade/upgrade-5.8.0d2-5.8.0d3.sql
  1. … 7 more files in changeset.
Merged oacs-5-7 to HEAD

  1. … 167 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
    ./postgresql/upgrade/upgrade-5.8.0d1-5.8.0d2.sql
  1. … 3 more files in changeset.
Bring PostgreSQL functions closer to the current level of PL/pgSQL:

- upgrade PL/pgSQL functions to the $$ notation (recommended since pg8.0, jan 2005).

- get rid of backslash usages in function definitions

- drop aliases in favor of named function arguments (recommended since pg8.0)

- fix wrong function_args, add missing function_args, align default semantics

with the defaults in pg (providing "null" as default means the argument is

optional).

- change return types of triggers from "opaque" to "trigger" (recommended since pg8.0)

- unify names of triggers *_tr

- removed some version dependencies of pg 7.2 and 7.3

    • -33
    • +69
    ./postgresql/acs-logs-create.sql
    • -219
    • +353
    ./postgresql/acs-metadata-create.sql
    • -40
    • +85
    ./postgresql/acs-object-util.sql
    • -446
    • +693
    ./postgresql/acs-objects-create.sql
    • -78
    • +167
    ./postgresql/acs-permissions-create.sql
    • -109
    • +204
    ./postgresql/acs-relationships-create.sql
    • -813
    • +1375
    ./postgresql/apm-create.sql
    • -7
    • +14
    ./postgresql/authentication-drop.sql
    • -47
    • +49
    ./postgresql/authentication-package-create.sql
    • -242
    • +368
    ./postgresql/community-core-create.sql
    • -309
    • +592
    ./postgresql/groups-body-create.sql
    • -82
    • +114
    ./postgresql/groups-create.sql
  1. … 40 more files in changeset.
    • -0
    • +297
    ./postgresql/upgrade/upgrade-5.7.0d10-5.7.0d11.sql
    • -197
    • +0
    ./postgresql/upgrade/upgrade-5.7.0d9-upgrade-5.7.0d10.sql
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
    ./postgresql/upgrade/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

    • -0
    • +0
    ./postgresql/upgrade/upgrade-5.7.0d10-5.7.0d11.sql
- 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
    ./postgresql/upgrade/upgrade-5.7.0d10-5.7.0d11.sql
  1. … 1 more file 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
    ./postgresql/upgrade/upgrade-5.7.0d9-upgrade-5.7.0d10.sql
  1. … 2 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
    ./postgresql/upgrade/upgrade-5.7.0d8-5.7.0d9.sql
  1. … 1 more file in changeset.
Fixing many bugs

    • -0
    • +191
    ./postgresql/upgrade/upgrade-5.7.0d7-5.7.0d8.sql
    • -67
    • +0
    ./postgresql/upgrade/upgrade-5.7.0d7-upgrade-5.7.0d8.sql
Hopefully got the friggin' oracle stuff to work, not to mention finding

pg kernel bugs and acs-object-management bugs.

    • -46
    • +326
    ./oracle/acs-metadata-create.sql
    • -507
    • +0
    ./oracle/upgrade/upgrade-5.7.0d4-5.7.0d5.sql
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.

    • -19
    • +5
    ./postgresql/acs-metadata-create.sql
    • -0
    • +67
    ./postgresql/upgrade/upgrade-5.7.0d7-upgrade-5.7.0d8.sql
  1. … 1 more file in changeset.
Final version of the 5.7 oracle upgrade for acs-kernel (unless CR work

uncovers problems).

    • -13
    • +61
    ./oracle/upgrade/upgrade-5.7.0d6-5.7.0d7.sql
Intermediate check-in of kernel changes for 5.7

    • -0
    • +647
    ./oracle/upgrade/upgrade-5.7.0d6-5.7.0d7.sql
*** empty log message ***

Further bug fixing ... hopefully, testing with AOM will tell the tale.

Also bumped *info file.

  1. … 1 more file 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
    ./postgresql/upgrade/upgrade-5.7.0d5-5.7.0d6.sql
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
    ./postgresql/upgrade/upgrade-5.7.0d4-5.6.0d5.sql
  1. … 1 more file in changeset.
First cut at Oracle upgrade for enhanced acs_datatypes and create_type,

create_attributes functionality that's already been completed for PG.

DO NOT ATTEMPT TO USE, IT'S NOT FINISHED.

    • -0
    • +507
    ./oracle/upgrade/upgrade-5.7.0d4-5.7.0d5.sql
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.

    • -159
    • +493
    ./postgresql/acs-metadata-create.sql
    • -309
    • +5
    ./postgresql/upgrade/upgrade-5.7.0d3-5.7.0d4.sql
  1. … 4 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
    ./postgresql/upgrade/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.

- 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
    • +9
    ./oracle/upgrade/upgrade-5.7.0d2-5.7.0d3.sql
    • -0
    • +82
    ./postgresql/upgrade/upgrade-5.7.0d2-5.7.0d3.sql
  1. … 1 more file in changeset.
apm_parameter__get_value bug missed by merge apparently.

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.

    • -0
    • +19
    ./postgresql/upgrade/upgrade-5.6.0b1-5.6.0b2.sql
    • -1
    • +28
    ./postgresql/upgrade/upgrade-5.6.0d1-5.6.0d2.sql
  1. … 207 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
    ./postgresql/upgrade/upgrade-5.7.0d1-5.7.0d2.sql
  1. … 15 more files in changeset.