aboutsummaryrefslogtreecommitdiffstats
path: root/include/onepoll.php
Commit message (Collapse)AuthorAgeFilesLines
* provide storage for directory based reputation in the xlink table by setting ↵friendica2015-01-261-1/+1
| | | | xlink_static = 1, so that xlink_static = 0 is traditional poco linkages
* PostgreSQL support initial commitHabeas Codice2014-11-131-7/+8
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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-12/+9
| | | | 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.
* try to sort out walltowall translation for diaspora recipientsfriendica2014-09-191-1/+1
|
* This is long overdue - use a symblic constant NULL_DATE instead of the ↵friendica2014-09-081-1/+1
| | | | easily mis-typed sequence '0000-00-00 00:00:00'
* get out the sunniesfriendica2014-08-311-3/+14
|
* onepoll: don't poll archived, blocked, or ignored connectionsfriendica2014-08-241-0/+2
|
* change flags for one-way connections from hidden to unconnected so we can ↵friendica2014-03-041-5/+2
| | | | still use hidden for - well hiding connections
* pull in some posts when we first connect with a new channel (if allowed to) ↵friendica2013-11-171-6/+18
| | | | - if not allowed to, do it if that condition changes
* populate some posts when somebody is granted "read stream" permissionfriendica2013-11-171-3/+6
|
* figure out why poller isn't picking up old posts which failed to deliverfriendica2013-08-291-4/+5
|
* start formatting for Doxygenfriendica2013-02-251-1/+1
|
* mark for death implementedfriendica2013-01-291-10/+8
|
* missing permission settingsfriendica2013-01-291-1/+2
|
* convert mod/follow to associative json and add more logging for when things ↵friendica2013-01-291-4/+2
| | | | go wrong
* poco debugging cont.friendica2013-01-251-2/+11
|
* here's another reason the social graph isn't updatingfriendica2013-01-241-0/+1
|
* why oh why is poco_load not getting called? oh - that's why.friendica2013-01-241-2/+2
|
* some poco fixesfriendica2013-01-221-5/+3
|
* json_decode param missingfriendica2013-01-031-1/+1
|
* temporary feed import/export (public only for the moment) until this is ↵friendica2013-01-031-0/+19
| | | | integrated with remote permissions
* another typofriendica2013-01-021-1/+1
|
* start building social graphfriendica2013-01-011-10/+8
|
* update timestamps on successful pollfriendica2012-12-301-2/+5
|
* refresh now works on poller runsfriendica2012-12-301-10/+9
|
* fixesfriendica2012-12-301-1/+1
|
* more progress on onepollfriendica2012-12-301-161/+19
|
* progress on pollerfriendica2012-12-301-40/+31
|
* fixed several little nit bugs that cropped up during deploymentfriendica2012-12-061-1/+1
|
* rm pidfile stuff since we won't need poller lockingfriendica2012-11-291-1/+0
|
* "profile url" e.g. the wall/stream is now "channel url". "Profile URL" goes ↵friendica2012-10-291-1/+1
| | | | to the profile details.
* more DB cleanupfriendica2012-08-301-45/+16
|
* eliminate the obsolete "last-child" indicatorfriendica2012-07-181-223/+0
|
* fix check for parent of StatusNet API postZach Prezkuta2012-06-251-1/+1
|
* rev updatefriendica2012-06-161-10/+0
|
* redundant log entryfriendica2012-06-141-1/+0
|
* also mark for death if there isn't any xml to be foundfriendica2012-06-141-0/+3
|
* poll even if contact hasn't responded recently, so we can update the ↵friendica2012-06-141-4/+2
| | | | termination status
* better handling of dead contactsfriendica2012-06-141-1/+4
|
* variable confusion in poller, don't allow negative page offsetsfriendica2012-06-111-2/+2
|
* ostatus hub subscription issuesfriendica2012-06-071-0/+3
|
* don't throw "did not contain xml" error if it's a valid rss that doesn't ↵friendica2012-05-071-1/+1
| | | | have the <?xml declaration
* If a contact has had delivery issues in the last 15 minutes, send new posts ↵friendica2012-05-071-0/+4
| | | | | | | 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.
* adding zrl support to social graphsfriendica2012-05-011-1/+1
|
* a few more continues that should be returnsfriendica2012-04-281-7/+7
|
* poller refactor: continue not valid in this contextfriendica2012-04-281-1/+1
|
* break up poller into separate processesfriendica2012-04-271-0/+519
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-05 11:44:32 +0000