• last updated 6 hours ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
[PostgreSQL 11] Change 'with (iscachable)' to IMMUTABLE for PG11

Replace obsolete function bitfromint4() by cast

  1. … 2 more files in changeset.
Replace obsolete funktion bittoint4() by cast

  1. … 2 more files in changeset.
merged changes from the oacs-5-9 branch and resolved conflicts

  1. … 7834 more files in changeset.
Merging back to HEAD branch oacs-5-8 (using tag vg-merge-oacs-5-8-from-20141027).

  1. … 2547 more files 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.

  1. … 3 more files in changeset.
- fix collateral damage

- add more cases of $$ quoting

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

  1. … 54 more files in changeset.
Some very archaic PG code that was only working because of weak type checking

in earlier versions. Uncovered by playing with the subsite admin object type

code.

- drop_package('...') complain in new versions that it can't drop

some stored procedures. Adding therefore a CASCADE to

the get_func_drop_command().

Fixed type mismatch problem due to tightened up PG 8.3 semantics.

Merged acs-core oacs-5-2 (currently 5.2.3) -> HEAD.

TODO:

1. Bump acs-core package version numbers to 5.3.0d1

2. Would be nice to do a test install, wouldn't it?

  1. … 721 more files in changeset.
Fixes bug #2300.

add an explicit cast of proname in drop_package needed in pg8

  1. … 2 more files in changeset.
fix some bugs which break things in pg7.5; mostly syntax errors in existing procs.

  1. … 4 more files in changeset.
trim function name and args in define_function_args to avoid difficult to track down problems when calling package_plsql_exec et al

merge of changes on oacs-5-0 branch to oacs-5-0-0b4 tag

  1. … 598 more files in changeset.
casts in tree_left and tree_right (pg 7.4 needs them it seems), bump version to 5.0a5, upgrade script provided

  1. … 2 more files in changeset.
Merged with 4.6 branch

  1. … 30 more files in changeset.
Patches to make OpenACS PG 7.3 compatible.

  1. … 54 more files in changeset.
Fix user_tab_comments view so it works on 7.2 (adds objsubid = 0)

added tree_increment_key() function

PG-7.2.1 returns false for 0<2^7. strange indeed. 2^7>0 returns true

Minor typo, another apostrophe catastrophe.

Added "iscachable" to "tree_ancestor_p".

Moved from 7/15 bit keys to 7/31 bit keys to accomodate big flat trees.

fixed instr for searching backwards

Renamed a column named "timestamp" in the security package because this is

now a reserved word in PG (correctly). I changed the Oracle version, too,

because I know that 9i has added the "timestamp" datatype and even if it

will accept it as a column name it's confusing.

I also changes postgresql.sql to load correctly under PG 7.1 and 7.2.

  1. … 8 more files in changeset.