aboutsummaryrefslogtreecommitdiffstats
path: root/mod/siteinfo.php
Commit message (Collapse)AuthorAgeFilesLines
* added dbdriver to siteinfo json to better track affected sitesHabeas Codice2014-11-221-1/+3
|
* 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)
* Show tag in siteinfo. Not useful for us, quite useful for admins.Thomas Willingham2014-10-111-1/+4
|
* it's probably better to return an int type in jsontuscanhobbit2014-10-081-1/+2
|
* The simplest way to hide hubs in statisticstuscanhobbit2014-10-081-1/+2
|
* site language in siteinfo/json has been re-addedPaolo Tacconi2014-10-021-0/+1
|
* query for statistics are now executed by pollerPaolo Tacconi2014-10-021-49/+9
|
* site language was left out of siteinfotuscanhobbit2014-10-011-0/+1
|
* added directory status to siteinfoPaolo Tacconi2014-09-301-1/+3
|
* Numbers shouldn't be stringsPaolo Tacconi2014-09-291-2/+2
|
* added statistics to siteinfo jsontuscanhobbit2014-09-281-2/+50
|
* allow the site to designate an admin channel that's visible to the outside ↵friendica2014-09-141-1/+7
| | | | world (via siteinfo/json). Otherwise we'll use the default channel of any accounts that have the account admin role.
* sort the plugins to make it easier to compare listsfriendica2014-09-111-0/+1
|
* and then make it even more usefulfriendica2014-09-111-0/+7
|
* make siteinfo/json useful againfriendica2014-09-111-14/+19
|
* convert application strings to en-USfriendica2014-07-311-1/+1
|
* !@#$% pay~!@#$palfriendica2014-03-041-18/+0
|
* update the donation linkfriendica2014-02-171-3/+3
|
* since the project donate section was added to siteinfo - add a way for the ↵friendica2014-02-091-6/+12
| | | | hub admin to add in a donation section to keep the hub running.
* provide donation options on siteinfo pagefriendica2014-02-011-1/+17
|
* Add admin info to admin panel and site info.Thomas Willingham2014-01-241-0/+4
| | | | Since we can have multiple admins, this is freeform bbcode.
* provide git revision in siteinfo if possible and if not instructed otherwisefriendica2013-12-181-4/+16
|
* too many friendica references in the siteinfo panelfriendica2013-11-121-5/+5
|
* begin to cut the umbilicalfriendica2013-04-141-3/+3
|
* add siteinfo.tplMichael Johnston2013-02-201-23/+21
|
* fix register_policy globallyfriendica2013-01-031-1/+1
|
* make the json workfriendica2012-11-161-1/+1
|
* site/friendica is now site/siteinfofriendica2012-11-161-0/+100