Revisions for framework/History/History.php

MFH:
1.432     +2 -2      framework/Form/Form.php
1.113     +3 -3      framework/Group/Group.php
1.61      +3 -3      framework/History/History.php
1.680     +5 -5      framework/Horde/Horde.php
1.24      +14 -14    framework/Kolab/Kolab/IMAP.php
1.9       +10 -9     framework/Kolab/Kolab/LDAP.php
1.68      +2 -2      framework/Notification/Notification.php
1.103     +2 -2      framework/Perms/Perms.php
1.175     +2 -2      framework/UI/UI/VarRenderer/html.php
1.27      +3 -6      framework/VC/VC.php

Tags: HORDE_3_2_1

Last round of singleton/reference fixes. I'm so looking forward to cleaning this
stuff up with PHP 5+ code.
Bug: 6837
Submitted by: Thomas Jarosch <thomas (dot) jarosch (at) intra2net (dot) com>

MFH: 1.60

Correctly check for disabled SQL configuration; reduce indention.
Bug: 6835

MFH 1.59

Tags: HORDE_3_2, HORDE_3_2_RC4

Check for errors from nextId()

Happy New Year

Tags: HORDE_3_2_RC3, HORDE_3_2_RC2

Happy New Year

Merge from HEAD.

Parameter check.
Bug: 4984

Tags: BEFORE_MERGE_3_2, HORDE_3_2_RC1, HORDE_3_2_ALPHA

Happy New Year

Tags: HORDE_3_1_8, HORDE_3_1_7, HORDE_3_1_6, HORDE_3_1_5, HORDE_3_1_4, HORDE_3_1_4_RC1

Happy New Year

Assign copyright to The Horde Project for those copyright holders that already agreed to it.

use isset instead of empty to allow supplying empty values

remove BC break for now. will probably need to fetch and delete
histories, or rely on perhaps being able to pass a wildcar id to
removeByNames().

Revert

Tags: HORDE_3_1_3, HORDE_3_1_2

MFH 1.48

@since

Bind variables.

fix indent, remove double semicolon.

remove stray newline

Added removeByParent to allow cleanup of history data during removeUserData.

MFH: Make sure to check that we got a valid result back from getHistory()
before doing anything with it.
Bug: 3560

Tags: HORDE_3_1_1, HORDE_3_1

Make sure to check that we got a valid result back from getHistory()
before doing anything with it.
Bug: 3560

MFH: 1.46

Database drivers extend DB_common, not DB.

Bug: 3482

MFH 1.45: don't throw errors switching in $phptype if the connection failed.

Tags: HORDE_3_1_RC3

no errors if connecting to the db fails

MFB 1.28.2.9

Fix typo

Tags: HORDE_3_1_RC2

MFH

use DB_PORTABILITY_RTRIM for mssql connections

MFH 1.42

Don't throw fatal errors if SQL is disabled.
Bug: 3232

Happy new year

Tags: HORDE_3_1_RC1

Happy new year\!

Remove comment relating to some other piece of code.

Updates for SQL split servers
- use the seperate server parameters, they were being ignored before
- add split support to the History API
- default to the write server, not the read server
- create the _write_db connection in the SQL sessionhandler

MFH: Fixes for reference warnings with PHP 5.1.

Fixes for reference warnings with PHP 5.1. If someone could merge
these it'd be appreciated, I'm not up to it right now and will be
swamped come morning.

Merged from HEAD.

Make sure portability option is set on when using databases.

Tags: BEFORE_MERGE_3_1

log() says it returns PEAR_Error or true.  So really make it return PEAR_Error
or true.

[cjh] Move Horde_History data to its own SQL table (Bug #2298).

I think this leaves only the code that's actually used.

Remove methods that have never been used.

MFH: Remove "@access public" and fix formatting/wrapping.

Tags: HORDE_3_0_12, HORDE_3_0_11, HORDE_3_0_10, HORDE_3_0_9, HORDE_3_0_8, HORDE_3_0_7, HORDE_3_0_6, HORDE_3_0_6_RC1, HORDE_3_0_5, HORDE_3_0_5_RC2, HORDE_3_0_5_RC1

Remove "@access public" and fix formatting/wrapping.

Clean up phpdoc.

Clean up phpdoc.

syncing updates

Submitted by: Karsten Fourmont <fourmont@gmx.de>

Happy New Year

Happy New Year

Tags: HORDE_3_0_4, HORDE_3_0_4_RC2, HORDE_3_0_4_RC1, HORDE_3_0_3, HORDE_3_0_3_RC1, HORDE_3_0_2, HORDE_3_0_1

Instead of hardcoding '-1' in tons of places, use a new constant: DATATREE_ROOT. Much more readable, etc. At the same time, make this an int (-1) instead of the string value ('-1') which was inconsistent with all other datatree ids, buggy, etc.

Tags: FRAMEWORK_3, HORDE_3_0

MFH

Adding app: is incorrect and causes odd errors.

Tags: HORDE_3_0_RC3

Attempt to speed up message deletion with batch history deletion.

Tags: FRAMEWORK_3_RC1

!isset() -> empty()

Move getTSforAction() to Horde_History class.

phpdoc fixes
Bug:
Submitted by: Andrew Coleman <mercury@appisolutions.net>
Merge after:

Fix method call.

Don't store log descriptions. They only consume space and make it impossible
to generate a different message from the log data, e.g. in a different
language.

More cleanups.

Comment cleanups.

When we just want to check position, strpos and stripos are faster and use less memory
than strstr and stristr.

No more HORDE_LIBS.

Random PHP 5 fixes:
- "clone" is a reserved word now.
- Only pass arrays to array functions.
- Don't cast objects to booleans.

Tags: HORDE_3_0_ALPHA

method/API changes

- Move Category into the framework.
- At the same time, rename the API to DataTree.
- shorten some method names while we're at it.

Happy new year everyone.

More attempts to fix @package tags and at least organize everything
correctly.

- add _getHistories() for batch fetching of history objects
- return the actual history objects, not just their ids, in getByTimestamp()

bring left a little bit

Allow filtering by parent history object

Transparently add the current application as the category parent of all
history objects.
You can override this by passing in a parent explicitly in the $guid.

This loses existing History data, sorry.

Use the new join support to get history filters to work correctly.

Add getByTimestamp() - lets you get entries based on the timestamp field, and
possibly filter on other fields as well.

tweak a few things for ease of using &getHistory()

Add an optional argument to $history->log() to replace an entry with the same 'action' parameter,
instead of adding a new one.

- add clone
- method and variable naming

I've given up on keeping histories with messages when the messages are
moved, though - we don't know the new uid of the message, so I'm just
not sure how to do it or what to identify the message with.

First crack at a completed, working Horde_History system Comments welcome.

Stub of a Horde_History class for tracking changes to any Horde item. Doesn't do anything yet.