aboutsummaryrefslogtreecommitdiffstats
path: root/install
Commit message (Collapse)AuthorAgeFilesLines
* dummy updateredmatrix2015-07-301-1/+6
|
* no this isn't it. well ok, it's part of it, but not the important part. it's ↵redmatrix2015-06-283-1/+15
| | | | still pretty cool.
* add site_dead flag to prevent delivery to dead sites. Allow sys channel ↵redmatrix2015-06-083-2/+17
| | | | webpages to be viewed even if site is configured "block public".
* add menu_created, menu_edited fields to DBredmatrix2015-05-283-2/+32
|
* Document php-xml requirement for webdav.Alexandre Hannud Abdo2015-05-191-2/+4
|
* provide default permissions ('all') for existing and newly created OAuth app ↵redmatrix2015-05-141-2/+23
| | | | clients, which will be extended in the future to allow specific permissions.
* Updated INSTALL.txt - outdated link correctedOliver Lorenz2015-04-281-1/+1
|
* update resource linksfriendica2015-04-011-2/+2
|
* add channel_lastpost timestamp to help optimise some outrageously expensive ↵friendica2015-03-263-1/+19
| | | | queries.
* we upped the php version requirement. So up yours.friendica2015-03-181-1/+1
|
* mysql schema typo, do the install check for store before chcking smarty, as ↵friendica2015-03-152-3/+3
| | | | that is where the dir is created, change install doc to point to install/schema_xxxxx.sql instead of database.sql
* sql optimisation for affinity searches. A new index was added which wasn't ↵friendica2015-03-102-1/+3
| | | | added retro-actively to existing DBs as an update. It isn't clear if this helps sites any more than just restricting the abook table to certain channel_id's is (and this field is already indexed).
* add queue priorityfriendica2015-03-043-2/+15
|
* finish converting "delete" to trash icons for consistency. The 'x' was left ↵friendica2015-02-261-2/+6
| | | | in a couple of places like the group list widget and saved search term widget and ignoring friend suggestions where it was more appropriate to leave it.
* fix issues in schema_postgres.sqlDaniel Frank2015-02-261-2/+2
| | | | - change PRIMARY_KEY to PRIMARY KEY - replace smallint(1) with smallint
* require access token to view, query, or join directories in private realms, ↵friendica2015-02-243-2/+14
| | | | if the realm is so configured.
* updated install docfriendica2015-02-201-11/+19
|
* update the install doc for addons - the procedure is a bit different now ↵friendica2015-02-191-4/+6
| | | | (although it shouldn't break anything on existing sites.)
* make sql work on both db typesHabeas Codice2015-02-131-1/+1
|
* provide relief to sites that are severely impacted by the slow ITEM_UNSEEN ↵friendica2015-02-123-1/+15
| | | | searches. This does not incorporate any other flag optimisations as that will require a major DB update and possibly involve significant downtime. This is just to bite off a little chunk now and provide some much needed relief.
* make update 1133 work in PHP < 5.5zottel2015-02-101-1/+1
|
* Merge branch 'master' of https://github.com/friendica/redHabeas Codice2015-02-053-2/+11
|\
| * admin/dbsync not reporting failed updatesfriendica2015-02-011-1/+1
| |
| * two tracks proceeding in parallel - first adding the ability to store a ↵friendica2015-02-013-1/+10
| | | | | | | | digital signature with ratings so that directories can pass them around, second provide some directory registration functions so we can obtain a list of directories from somewhere (to pass ratings around between them). This gives the primary directory role some value as that is where you register your directory.
* | typo/cleanup pg onlyHabeas Codice2015-02-051-4/+5
|/
* Add more detail about directory_mode settings to default config and docsHabeas Codice2015-01-301-4/+4
|
* postgres does not support the , syntax. a ; would work, if it weren't ↵Habeas Codice2015-01-281-1/+3
| | | | | | | statement-locked. FWIW, the exact same queries listed for postgres are perfectly valid and equivalent on mysql. no need for separate statements.
* provide storage for directory based reputation in the xlink table by setting ↵friendica2015-01-263-2/+17
| | | | xlink_static = 1, so that xlink_static = 0 is traditional poco linkages
* typoHabeas Codice2015-01-251-1/+1
|
* update schemaHabeas Codice2015-01-251-1/+1
|
* suppress notices that might be confusingHabeas Codice2015-01-251-2/+2
|
* unmatched parensHabeas Codice2015-01-231-1/+1
|
* add db update 1131/1132 to database schemaszottel2015-01-232-0/+4
|
* typo in postgres db update, remove redmatrix.nl from directory servers since ↵friendica2015-01-201-1/+1
| | | | it isn't a directory server any more.
* oauth permissions tablefriendica2015-01-193-2/+58
|
* fix update 1131 for postgres databasesHabeas Codice2015-01-181-1/+14
|
* more backend work on poco ratingfriendica2015-01-151-1/+11
|
* fix driver issue for large dbsHabeas Codice2014-11-201-25/+76
| | | | add rudimentary resume
* simple command-line migrator from mysql to postgresHabeas Codice2014-11-172-0/+361
| | | | provided with the WorksForMe(tm) warranty of fitness for a purpose implied or otherwise
* Merge remote-tracking branch 'upstream/master'Habeas Codice2014-11-133-191/+2488
|\ | | | | | | | | | | | | | | | | | | | | | | 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
| * add defaults to database tablesfriendica2014-11-092-190/+2467
| |
| * ok heads up - potentially destabilising change. I've tried to sort out all ↵friendica2014-11-041-1/+21
| | | | | | | | | | | | | | | | | | | | the default connection permissions for those who don't have a predefined (or therefore have a "custom") permissions role. Unfortunately this includes most people that were using this software more than a month ago. The real changes are that the SELF address book entry no longer holds "auto-permissions" but instead holds your "default permissions" (if you have a pre-defined role, the defaults will be pulled from the role table). The auto permissions have moved to a pconfig (uid.system.autoperms). A DB update will move these settings into their new homes. What used to be the "Auto-permissions settings" page is now the "default permissions settings" page and a checkbox therein decides whether or not to apply the permissions automatically. A link to this page will only be shown when you have the "custom" role selected. With luck nobody will notice anything wrong. But at least for the next few days, please review permissions that have been assigned to new connections (either automatically or manually) and make sure they make sense (e.g. they aren't "nothing"). You still need to take action when seeing a message "permissions have changed but not yet submitted" as we always let you review and perhaps adjust the settings _before_ a connection is established (unless you have autoperms turned on).
* | PostgreSQL support initial commitHabeas Codice2014-11-132-0/+1190
|/ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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)
* Doco - some clean up to install - keep politics out of it, 80 columnise it andThomas Willingham2014-10-221-63/+63
| | | | whitespace.
* document store writability requirementszottel2014-10-221-2/+3
|
* missing quotefriendica2014-10-141-1/+1
|
* this is the reason Diaspora forum tagging was brokenfriendica2014-10-141-1/+8
|
* install doc double escapes the store/[data] path.friendica2014-10-061-1/+1
|
* +png supportjeroenpraat2014-10-051-1/+1
| | | https://redmatrix.nl/channel/jeroenpraat/?f=&mid=83603d8f0876c040efafce87755fcd252dbe8da4a75d82fdb230519e3c8dcb72@redmatrix.nl
* store diaspora meta info in the item table. It has to go there or it will ↵friendica2014-09-032-1/+11
| | | | kill us with complex joins. We can phase out the sign table once this all checks out.
generated by cgit v1.2.3 (git 2.25.1) at 2024-12-02 05:45:08 +0000