aboutsummaryrefslogtreecommitdiffstats
path: root/include/expire.php
Commit message (Collapse)AuthorAgeFilesLines
* DB changes for some channel flagsredmatrix2015-06-151-1/+1
|
* first cut at merging files and photos, not yet well integrated but they are ↵redmatrix2015-06-141-1/+0
| | | | integrated
* more work on item table optimisationredmatrix2015-06-101-3/+2
|
* Merge branch 'master' into tresfriendica2015-04-231-24/+60
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Conflicts: include/Contact.php include/ItemObject.php include/api.php include/attach.php include/diaspora.php include/dir_fns.php include/enotify.php include/event.php include/expire.php include/items.php include/notifier.php include/notify.php include/photos.php include/taxonomy.php include/text.php include/widgets.php include/zot.php mod/admin.php mod/channel.php mod/dirsearch.php mod/display.php mod/editwebpage.php mod/events.php mod/home.php mod/item.php mod/manage.php mod/mood.php mod/network.php mod/page.php mod/photos.php mod/ping.php mod/post.php mod/thing.php mod/viewsrc.php view/css/mod_events.css
| * Correcting reported Doxygen syntax warnings.Klaus Weidenbach2015-03-291-31/+28
| | | | | | | | | | | | | | Fixed wrong Doxygen syntax and add some of the available FIXME to Doxygen documentation. Updated Doxygen configuration to add also all capital letter tags. Adding some more Doxygen documentation.
| * also allow service classes to set post expiration. These take priority over ↵friendica2015-03-241-10/+12
| | | | | | | | the site default.
| * more work on expiration, make system limits useful - even in retrospectfriendica2015-03-241-9/+25
| |
| * make the log message reflect what's really happeningfriendica2015-03-241-1/+3
| |
| * provide a site-wide expiration policy without loopholes - still need work to ↵friendica2015-03-241-8/+28
| | | | | | | | reduce the impact of expiration queries.
* | start on item_restrict conversionfriendica2015-01-221-2/+1
|/
* PostgreSQL support initial commitHabeas Codice2014-11-131-4/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | There were 11 main types of changes: - UPDATE's and DELETE's sometimes had LIMIT 1 at the end of them. This is not only non-compliant but it would certainly not do what whoever wrote it thought it would. It is likely this mistake was just copied from Friendica. All of these instances, the LIMIT 1 was simply removed. - Bitwise operations (and even some non-zero int checks) erroneously rely on MySQL implicit integer-boolean conversion in the WHERE clauses. This is non-compliant (and bad programming practice to boot). Proper explicit boolean conversions were added. New queries should use proper conventions. - MySQL has a different operator for bitwise XOR than postgres. Rather than add yet another dba_ func, I converted them to "& ~" ("AND NOT") when turning off, and "|" ("OR") when turning on. There were no true toggles (XOR). New queries should refrain from using XOR when not necessary. - There are several fields which the schema has marked as NOT NULL, but the inserts don't specify them. The reason this works is because mysql totally ignores the constraint and adds an empty text default automatically. Again, non-compliant, obviously. In these cases a default of empty text was added. - Several statements rely on a non-standard MySQL feature (http://dev.mysql.com/doc/refman/5.5/en/group-by-handling.html). These queries can all be rewritten to be standards compliant. Interestingly enough, the newly rewritten standards compliant queries run a zillion times faster, even on MySQL. - A couple of function/operator name translations were needed (RAND/RANDOM, GROUP_CONCAT/STRING_AGG, UTC_NOW, REGEXP/~, ^/#) -- assist functions added in the dba_ - INTERVALs: postgres requires quotes around the value, mysql requires that there are not quotes around the value -- assist functions added in the dba_ - NULL_DATE's -- Postgres does not allow the invalid date '0000-00-00 00:00:00' (there is no such thing as year 0 or month 0 or day 0). We use '0001-01-01 00:00:00' for postgres. Conversions are handled in Zot/item packets automagically by quoting all dates with dbescdate(). - char(##) specifications in the schema creates fields with blank spaces that aren't trimmed in the code. MySQL apparently treats char(##) as varchar(##), again, non-compliant. Since postgres works better with text fields anyway, this ball of bugs was simply side-stepped by using 'text' datatype for all text fields in the postgres schema. varchar was used in a couple of places where it actually seemed appropriate (size constraint), but without rigorously vetting that all of the PHP code actually validates data, new bugs might come out from under the rug. - postgres doesn't store nul bytes and a few other non-printables in text fields, even when quoted. bytea fields were used when storing binary data (photo.data, attach.data). A new dbescbin() function was added to handle this transparently. - postgres does not support LIMIT #,# syntax. All databases support LIMIT # OFFSET # syntax. Statements were updated to be standard. These changes require corresponding changes in the coding standards. Please review those before adding any code going forward. Still on my TODO list: - remove quotes from non-reserved identifiers and make reserved identifiers use dba func for quoting - Rewrite search queries for better results (both MySQL and Postgres)
* try and sort out the item delete messfriendica2014-03-271-2/+14
|
* firehose: provide system prefs to allow folks to fine tune to their needsfriendica2014-03-271-2/+11
|
* more work on firehosefriendica2014-03-261-0/+4
|
* protect filed conversations from expiration - we check the parent to see if ↵friendica2014-03-111-1/+1
| | | | it is filed, but one may have filed a comment and that will vanish when the parent expires unless the parent is protected.
* start formatting for Doxygenfriendica2013-02-251-1/+1
|
* more heavy liftingfriendica2012-10-231-31/+12
|
* make it optional to optimize the item table after expirefriendica2012-05-081-1/+5
|
* Merge branch 'master' of https://github.com/friendica/friendicaAlexander Kampmann2012-04-051-0/+0
| | | | | | Conflicts: include/config.php update.php
* do an optimise after an expungefriendica2012-02-021-2/+2
|
* prune old expired and deleted itemsfriendica2012-01-301-0/+5
|
* add remove_user hook (it looks like dreamhost changed all my file ↵friendica2012-01-181-0/+0
| | | | permissions, this will make a nasty commit)
* load db configs (config,system) for all "executables"Friendika2011-06-301-0/+4
|
* bug #96 move libraries to library - better alignment of like rotatorFriendika2011-06-281-3/+3
|
* content expirationFriendika2011-03-151-0/+44