aboutsummaryrefslogtreecommitdiffstats
path: root/include/deliver.php
Commit message (Collapse)AuthorAgeFilesLines
* another tactic to deal with orphan hublocs from re-installs, or at least ↵redmatrix2015-09-111-2/+2
| | | | allow the descendant channel to survive
* add site_dead flag to prevent delivery to dead sites. Allow sys channel ↵redmatrix2015-06-081-8/+17
| | | | webpages to be viewed even if site is configured "block public".
* more work on queue optimisationsfriendica2015-03-091-0/+10
|
* missing commafriendica2015-03-041-1/+1
|
* don't re-use $xfriendica2015-03-041-2/+2
|
* add queue priorityfriendica2015-03-041-0/+18
|
* Merge remote-tracking branch 'upstream/master'Habeas Codice2014-11-131-2/+5
|\ | | | | | | | | | | | | | | | | | | | | | | Conflicts: boot.php include/dba/dba_driver.php include/diaspora.php include/follow.php include/session.php include/zot.php mod/photos.php mod/ping.php
| * I'm going to try again with the conversation request packets. I've looked ↵friendica2014-11-021-2/+5
| | | | | | | | this over and tested a lot of edge cases, and thought about from every angle I can think of to prevent looping. I don't *think* this can loop. I also doubt that this is the problem at friendicared.de, but I don't know for sure what that problem might be.
* | PostgreSQL support initial commitHabeas Codice2014-11-131-4/+4
|/ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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)
* What this checkin does is catch the case where a comment arrived and there's ↵friendica2014-10-301-4/+19
| | | | a missing top-level post to match it with. So we'll send a request back to the sender that you've never seen this thread and please send a fresh copy of the entire conversation to date. We could soon have posts in the matrix from different platforms from days gone by, which have been migrated into the modern world. We'll be polite and not deliver these to everybody. However, if someone comments on one of these antique threads we wouldn't be able to see it in our own matrix because we won't have a copy of the parent post. So this rectifies that situation. Be aware that item deletion may need to change to keep "hard deleted" items indefinitely so that they don't keep coming back. We'll have to null out the important data of the former item to accomplish the deletion aspect.
* various diaspora issuesfriendica2014-08-291-0/+1
|
* more queue tweaksfriendica2014-08-281-1/+1
|
* lots of little Diaspora issuesfriendica2014-08-281-0/+3
|
* works one way sort of - now to go the other way - which will require fixing ↵friendica2014-08-261-1/+1
| | | | a whole slew of FIXMEs
* take off the kid glovesfriendica2014-08-261-0/+14
|
* minor adjustmentsfriendica2014-07-011-1/+3
|
* issue #240 - we were using htmlentities instead of htmlspecialchars in ↵friendica2013-12-111-0/+1
| | | | several places, and this was a bit greedy in the set of characters which were converted from utf-8 to HTML entities. Also brought mail attachments up to date so they are rendered identically to item attachments.
* block forgeriesfriendica2013-10-021-1/+1
|
* push refresh messages, performance work on conversations and configs, doc ↵friendica2013-06-141-5/+8
| | | | updates
* start formatting for Doxygenfriendica2013-02-251-1/+1
|
* more delivery diagnosticsfriendica2012-12-311-1/+1
|
* local deliveryfriendica2012-12-021-7/+18
|
* DATABASE: outq additions, delivery now getting the notify across to the ↵friendica2012-11-191-0/+40
other side