aboutsummaryrefslogtreecommitdiffstats
path: root/mod/ping.php
Commit message (Collapse)AuthorAgeFilesLines
* Merge remote-tracking branch 'upstream/master'Habeas Codice2014-11-131-75/+117
|\ | | | | | | | | | | | | | | | | | | | | | | 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
| * class is a reserved wordfriendica2014-11-101-4/+4
| |
| * configurable visual alerts/notificationsfriendica2014-11-041-71/+113
| |
* | PostgreSQL support initial commitHabeas Codice2014-11-131-16/+18
|/ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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)
* make the pending connections query consistent between mod/ping and ↵friendica2014-07-051-5/+7
| | | | mod/connections
* more doco on mod/ping - plus fix a birthday notification which was a day off.friendica2014-06-301-6/+52
|
* Some documentation in mod/ping.php an reduced default logging.Klaus Weidenbach2014-06-301-47/+33
| | | | It is now LOGGER_DATA as it returns the json data contents.
* got the presence bit.friendica2014-04-261-1/+1
|
* This should resolve the dav authentication loop (correctly)friendica2014-02-221-1/+1
|
* prevent mod/cloud looping (ping gets a new session on each call [wtf?] which ↵friendica2014-02-221-1/+1
| | | | triggers our "changed uid" detector)
* mod/ping - don't perform any database calls if installingfriendica2014-02-061-0/+6
|
* mod/ping should only update basic_presence - and clearing stale entries. ↵friendica2014-01-301-9/+6
| | | | otherwise let rooms handle presence for themselves.
* prevent runaway presence indicationfriendica2014-01-291-2/+2
|
* issues uncovered whilst testing the chatroom APIfriendica2014-01-291-3/+7
|
* chatpresence timing out too quicklyfriendica2014-01-281-1/+1
|
* fix sql query and provide setting to hide online statusfriendica2014-01-281-1/+1
|
* basic presence indicationfriendica2014-01-281-0/+25
|
* Fix new connection nav URLThomas Willingham2014-01-081-1/+1
|
* split private messages into two modules - "message" is just for message ↵friendica2013-12-211-1/+1
| | | | lists, "mail" is for reading and writing conversations. This is so we can Comanchify it cleanly.
* clicking on an event notification from somebody else should take you to view ↵friendica2013-11-131-1/+1
| | | | event - not edit event. Need to also check permissions on event module because reaching this form shouldn't have been possible without event write permissions.
* fix marking events seenfriendica2013-04-161-1/+1
|
* replace old intro linkfriendica2013-03-061-1/+1
|
* prevent repeated channel names in system notificationsfriendica2013-02-101-1/+1
|
* smarty support in intltext, fix old pending accounts query in ping, log ↵friendica2013-02-091-2/+4
| | | | failed email register notify
* debugging mark all seen for various notification typesfriendica2013-02-041-1/+2
|
* finish up the "mark all xyz seen" for all known values of xyzfriendica2013-02-031-0/+43
|
* mopping up the events issues so I can move on to other stufffriendica2013-01-161-2/+15
|
* typofriendica2013-01-161-0/+31
|
* still some bugs but events are happening again.friendica2013-01-151-3/+3
|
* fix the "personal" network filter and introduction notificationsfriendica2013-01-091-4/+4
|
* The rest of the front end for the new notifications - now only missing "mark ↵friendica2013-01-081-2/+2
| | | | all seen" for some types, ajax loader for a couple of types, and perhaps a birthday cake icon if any birthdays today, a bit of css cleanup of duplicated or obsolete stuff
* remove debuggingfriendica2013-01-081-3/+0
|
* lots of notification tweaksfriendica2013-01-081-0/+39
|
* fix register_policy globallyfriendica2013-01-031-1/+1
|
* fix event query - some DB's have problems with itfriendica2013-01-031-3/+3
|
* get notification backend working againfriendica2012-12-191-1/+1
|
* set_baseurl issue, more cleanupfriendica2012-12-191-13/+4
|
* DB: do the mail table again. Mail almost working onsite, still needs to zot ↵friendica2012-12-041-4/+5
| | | | though
* connection notificationsfriendica2012-12-021-2/+32
|
* further progress on new network/home notificationsfriendica2012-11-291-6/+6
|
* a bit more progress on the new network/home ajax notifications, at least ↵friendica2012-11-131-0/+1
| | | | I've now got a plan
* "profile url" e.g. the wall/stream is now "channel url". "Profile URL" goes ↵friendica2012-10-291-1/+1
| | | | to the profile details.
* fix updating of bitwise 'unseen' to account for mysql operator precedencefriendica2012-10-281-1/+1
|
* start on network/home notification refactorfriendica2012-10-271-1/+28
|
* start fixing all the item queriesfriendica2012-10-071-8/+5
|
* here's where the heavy lifting begins - everything is likely to be broken ↵friendica2012-10-011-1/+2
| | | | for quite some time as we add location and db independence to items and conversations and work through the rest of the permissions and how to federate the buggers.
* create a widget registry for pages so themes can reorder, insert/delete, and ↵friendica2012-09-271-2/+5
| | | | relocate widgets to different regions of the page
* trim a bit of fatfriendica2012-08-291-1/+1
|
* have to do something about that return_url - but let's just plunge forward ↵friendica2012-08-281-1/+1
| | | | without it.
* a few minor changesfriendica2012-08-261-3/+10
|
generated by cgit v1.2.3 (git 2.25.1) at 2024-12-22 12:34:22 +0000