aboutsummaryrefslogtreecommitdiffstats
path: root/mod/receive.php
Commit message (Collapse)AuthorAgeFilesLines
* PostgreSQL support initial commitHabeas Codice2014-11-131-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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 to sort out walltowall translation for diaspora recipientsfriendica2014-09-191-1/+1
|
* reduce log level of inbound d* posts until we get through some of the more ↵friendica2014-09-091-1/+1
| | | | serious federation issues
* D* receive endpoint is receive/users/$guid - where $guid is really the ↵friendica2014-08-211-4/+5
| | | | channel_guid, not the channel_hash. We'll allow this to be truncated for older D* sites or those that can't process our 64 character guids.
* change default invitation messagefriendica2014-08-111-1/+1
|
* nothing going on here. nothing to see. move along.friendica2014-08-101-0/+76
|
* Removing connectors we won't be needing - this is probably going to break ↵friendica2012-07-181-68/+0
| | | | some shit.
* Merge branch 'master' of https://github.com/friendica/friendicaAlexander Kampmann2012-04-051-0/+7
|\ | | | | | | | | | | Conflicts: include/config.php update.php
| * let's catch d* disabled at a higher level and not waste any resources on it.friendica2012-04-041-0/+7
|/
* add remove_user hook (it looks like dreamhost changed all my file ↵friendica2012-01-181-0/+0
| | | | permissions, this will make a nasty commit)
* cripple account when expiredFriendika2011-09-191-1/+1
|
* diaspora protocol changesFriendika2011-09-141-11/+23
|
* D* queueFriendika2011-08-241-28/+1
|
* diaspora photos ?Friendika2011-08-231-0/+3
|
* double url encode diaspora communicationsFriendika2011-08-191-0/+2
|
* D* like and start of relay codeFriendika2011-08-161-6/+6
|
* refactor the diaspora contact logicFriendika2011-08-151-40/+5
|
* turn diaspora posts into x-www-form-urlencodedFriendika2011-08-151-5/+13
|
* fixes share from diasporaFriendika2011-08-151-2/+2
|
* improved diaspora discoveryFriendika2011-08-121-1/+1
|
* diaspora function dispatcherFriendika2011-08-101-23/+36
|
* crypto stuffFriendika2011-08-091-1/+1
|
* diaspora encrypt+decrypt working !!Friendika2011-08-091-198/+6
|
* cleanupFriendika2011-08-071-1/+1
|
* fallback sha256 openssl_verify code for php releases prior to 5.3Friendika2011-08-051-3/+6
|
* updates to Diaspora decrypt/verify from recent testingFriendika2011-08-051-48/+14
|
* get_diaspora_key()Friendika2011-07-301-9/+31
|
* basic diaspora decryptionFriendika2011-07-301-31/+103
|
* wrong path for salmon verifyFriendika2011-07-201-1/+0
|
* diaspora salmon endpoint (decryption not yet provided)Friendika2011-07-191-0/+215