| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | put deferred queue logic every place we create a delivery process (except ↵ | zotlabs | 2017-11-02 | 1 | -8/+0 |
| | | | | | for protocol 'friend requests' which aren't likely to swamp the delivery system). Remove it from the queue_delivery function which was too late to do anything. | ||||
| * | add another delivery control parameter (force queue threshold) | zotlabs | 2017-10-31 | 1 | -1/+11 |
| | | |||||
| * | create site_store_lowlevel() to initialise data structures for the site table | zotlabs | 2017-04-03 | 1 | -4/+8 |
| | | |||||
| * | queue optimisations for sites that have lingered in the queue for more than ↵ | zotlabs | 2017-01-29 | 1 | -1/+16 |
| | | | | | a couple of days. | ||||
| * | Alter the queue so that each queue item stores the scheduled time of the ↵ | zotlabs | 2017-01-29 | 1 | -4/+42 |
| | | | | | | | | | next delivery. This keeps the query for queued items simple. We no longer group by posturl; as the queue update function will only keep one item per destination scheduled for shorter term processing. Others (multiple queued items for a single destination) will be scheduled for delivery far into the future and only delivered if the hub responds to the "active" or short term queue item. | ||||
| * | db update required for Zot2 | zotlabs | 2016-11-22 | 1 | -1/+1 |
| | | |||||
| * | sql: limit 1 for UPDATE and DELETE is not supported by the SQL standard and ↵ | Florian Steinel | 2016-10-27 | 1 | -1/+1 |
| | | | | | | | postgresql (see: https://www.postgresql.org/message-id/flat/1291109101.26137.35.camel%40pcd12478 ) | ||||
| * | backtrace openssl_verify errors so that we can find bad keys - as there is ↵ | redmatrix | 2016-02-25 | 1 | -2/+2 |
| | | | | | very little relevant context available at this level. | ||||
| * | hook changes to support pubsubhubbub | redmatrix | 2016-02-10 | 1 | -1/+1 |
| | | |||||
| * | log API improvements and queue optimisation for singleton networks | redmatrix | 2015-12-31 | 1 | -0/+20 |
| | | |||||
| * | make the queue api accessible to addons | redmatrix | 2015-12-21 | 1 | -1/+7 |
| | | |||||
| * | queue/notification/delivery refactor continued | redmatrix | 2015-12-16 | 1 | -0/+81 |
| | | |||||
| * | issue #221 | redmatrix | 2015-12-15 | 1 | -3/+17 |
| | | |||||
| * | more queue api | redmatrix | 2015-12-15 | 1 | -6/+19 |
| | | |||||
| * | simplify queue insertion for normal items | redmatrix | 2015-12-14 | 1 | -0/+19 |
| | | |||||
| * | PostgreSQL support initial commit | Habeas Codice | 2014-11-13 | 1 | -2/+2 |
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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) | ||||
| * | start formatting for Doxygen | friendica | 2013-02-25 | 1 | -1/+1 |
| | | |||||
| * | requeue failed deliveries | friendica | 2012-12-30 | 1 | -58/+4 |
| | | |||||
| * | more DB cleanup | friendica | 2012-08-30 | 1 | -1/+1 |
| | | |||||
| * | fix to imported youtube videos, updating of contact profile photos, do not ↵ | friendica | 2012-06-13 | 1 | -0/+7 |
| | | | | | remove "dead" contacts but archive them. | ||||
| * | finished dry run - now for real test | friendica | 2012-05-07 | 1 | -1/+3 |
| | | |||||
| * | If a contact has had delivery issues in the last 15 minutes, send new posts ↵ | friendica | 2012-05-07 | 1 | -0/+9 |
| | | | | | | | | straight to the queue and don't even try to connect. Also defer polling for stuck contacts. Should reduce the number of stuck processes trying to connect with dead or dying servers significantly. | ||||
| * | Merge branch 'master' of https://github.com/friendica/friendica | Alexander Kampmann | 2012-04-05 | 1 | -0/+0 |
| | | | | | | | Conflicts: include/config.php update.php | ||||
| * | add remove_user hook (it looks like dreamhost changed all my file ↵ | friendica | 2012-01-18 | 1 | -0/+0 |
| | | | | | permissions, this will make a nasty commit) | ||||
| * | fix queue_fns | Friendika | 2011-10-23 | 1 | -1/+4 |
| | | |||||
| * | queue api + queue limits | Friendika | 2011-10-21 | 1 | -0/+35 |
| | | |||||
| * | facebook queueing on failure, sync update.php with boot.php update version ↵ | Friendika | 2011-06-03 | 1 | -0/+16 |
| to avoid race condition | |||||
 |
index : volse-hubzilla.git | |
| Volse Hubzilla -- soft fork of main Hubzilla core for Volse | Harald Eilertsen |
| aboutsummaryrefslogtreecommitdiffstats |