• last updated 3 hours ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
bump version numbers to 5.9.1b9 respectively to 2.9.1b9 to prepare for release

  1. … 91 more files in changeset.
Fix typo in parameter name

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.

  1. … 12 more files in changeset.
Fix spelling errors

  1. … 49 more files in changeset.
Performance improvement in content_item__get_path stored procedure (thanks to Thomas Renner)

  1. … 2 more files in changeset.
- bump version number of OpenACS to 5.9.1b3 and DotLRN to 2.9.1b3

  1. … 79 more files in changeset.
Bump version numbers for OpenACS 5.9.1b1

  1. … 81 more files in changeset.
- Align type of parameter "storage_type" with type definition of cr_items.storage_type

- bump version to 5.9.1d27

  1. … 3 more files in changeset.
- fix bug when updateing a user portrait, which was saved as "lob"

  1. … 2 more files in changeset.
- 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

  1. … 2 more files in changeset.
- 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

  1. … 3 more files in changeset.
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

  1. … 3 more files in changeset.
Created new proc cr_check_mime_type, centralizing the retrieval of the mime_type from uploaded file's information.

Applied the new proc to the different situations in the system when we require mime_type retrieval: content-repository, file-storage and xotcl CrItem

TODO: get the real mime_type from the file content, but this would require some modification in the data model.

  1. … 7 more files in changeset.
Updated mimetypes

  1. … 2 more files in changeset.
- fix old typo in label of unknown mimtype (was "Unkown")

  1. … 3 more files in changeset.
- use consistently varchar(1000) for object_types

- bump version number to 5.9.1d19

  1. … 2 more files in changeset.
- avoid call of deprecated function

  1. … 1 more file in changeset.
- add missing enumeration type to create script

- fix ambiguity for content_item__new in template__new

- add/update mime types for text/csv text/vcard, text/calendar

- bump version number to 5.9.1d17

  1. … 6 more files in changeset.
- Change text enumeration field "storage_type" in cr_items to native

SQL enumeration type

- bump version number to 5.9.1d15

  1. … 3 more files in changeset.
- use newer style mimetype 'application/gzip' instead of

'application/x-gzip' as defined by IANA content types

- fix indentation in sql/common/mime-type-data.sql

- bump version number to 5.9.1d14

  1. … 3 more files in changeset.
- update mimetype definition of javascript to the form specified via IANA content types

- add JSON mimetpye

  1. … 2 more files in changeset.
- change mime type for .swf from "application/x-shockwave-flash" to IANA complient entry "application/vnd.adobe.flash-movie"

  1. … 3 more files in changeset.
- add more Open XML formats for MS-Office

  1. … 2 more files in changeset.
Content-Repository Reform: reduce dependency on cr_child_rels and make

creation of cr_child_rels entries optional. Most applications do not

need cr_child_rels, these take substantial space and slow down

operations. The change is fully backward compatible, since per

default cr_child_rels are still created. First tests show an

improvement for the creation of cr_items by 17% and for deletion by

28% (when parent item is a plain cr_item, as it is e.g. the case in

xwowiki). Same change made as well for Oracle.

- affected functions (here with pg-names)

* procedure content_item__new/21 (version for text or file entries) has new optional boolean parameter: with_child_rels

* procedure content_item__new/17 (version for blob entries) has new optional boolean parameter: with_child_rels

- remove/reduce dependency on cr_child_rels (if no rel-tag is used, the chile-information is obtained from cr_items)

* content_item__is_publishable/1

* content_item__is_valid_child/3

* content_item__is_valid_child/2

- reduce number of functions by using defaults

* content_item__copy/5

* content_item__get_title/2

* content_item__move/3

  1. … 4 more files in changeset.
- bump version number to 5.9.1d8

- bump version number

- Update automatically generated function for cr-types to use provided

publish_date in new revision (Changes for PostgreSQL and Oracle)

  1. … 4 more files in changeset.
- Bug-fix: Make sure, trigger content_item_search__utrg does try to

delete content from via search queue when old publish_date was in

the future (since this is avoided by the same trigger).

(Oracle seems to implement search quite different)

  1. … 2 more files in changeset.
- Add argument to content_item__set_live_revision (and oracle's counterpart)

to honor optionally provided "publish_date". The old behavior used hard-coded

the current time. The function is fully backward compatible, when no

publish_date is provided, the current time is used for the publish_date.

- changes for PostgreSQL and Oracle.

  1. … 4 more files in changeset.
- fix unclosed element