aboutsummaryrefslogtreecommitdiffstats
path: root/install/schema_postgres.sql
Commit message (Collapse)AuthorAgeFilesLines
* schema support for additional site typesredmatrix2015-09-281-0/+2
|
* add vdata field for caldavredmatrix2015-09-231-0/+1
|
* heavy lifting for delivery reportsredmatrix2015-09-221-0/+2
|
* DB table for delivery reportsredmatrix2015-09-181-0/+22
|
* add timestamps for syncing appsredmatrix2015-09-021-0/+4
|
* separate objs/things from taxonomyredmatrix2015-09-011-0/+10
|
* Merge https://github.com/redmatrix/redmatrix into pending_mergeredmatrix2015-08-311-0/+2
|\ | | | | | | | | | | | | | | Conflicts: include/identity.php install/update.php util/messages.po view/nl/messages.po
| * change the likes db structure to make it more easily importable/exportableredmatrix2015-08-311-0/+2
| |
* | Merge https://github.com/redmatrix/redmatrix into pending_mergeredmatrix2015-08-201-0/+2
|\|
| * missed this one - it's requiredredmatrix2015-08-201-0/+2
| |
* | Merge https://github.com/redmatrix/redmatrix into pending_mergeredmatrix2015-08-181-0/+2
|\|
| * add event_sequence for vtodo'sredmatrix2015-08-181-0/+2
| |
* | Merge https://github.com/redmatrix/redmatrix into pending_mergeredmatrix2015-08-161-0/+5
|\|
| * add DB support for tasks, todo items and repeating eventsredmatrix2015-08-161-0/+5
| |
* | fix the postgres schema with all the changes to dateredmatrix2015-06-291-3/+115
| |
* | Merge branch 'master' of https://github.com/redmatrix/redmatrixredmatrix2015-06-281-0/+2
|\| | | | | | | | | | | | | Conflicts: include/zot.php mod/connedit.php util/messages.po
| * no this isn't it. well ok, it's part of it, but not the important part. it's ↵redmatrix2015-06-281-0/+2
| | | | | | | | still pretty cool.
* | Merge branch 'master' of https://github.com/redmatrix/redmatrixredmatrix2015-06-091-0/+2
|\| | | | | | | | | | | | | | | | | Conflicts: install/schema_mysql.sql mod/home.php mod/page.php view/nl/messages.po view/nl/strings.php
| * add site_dead flag to prevent delivery to dead sites. Allow sys channel ↵redmatrix2015-06-081-0/+2
| | | | | | | | webpages to be viewed even if site is configured "block public".
* | Merge branch 'master' of https://github.com/redmatrix/redmatrixredmatrix2015-05-281-0/+4
|\| | | | | | | | | | | | | | | Conflicts: install/schema_mysql.sql mod/impel.php view/pt-br/messages.po view/pt-br/strings.php
| * add menu_created, menu_edited fields to DBredmatrix2015-05-281-0/+4
| |
* | convert ITEM_WALL from bitfield to standaloneredmatrix2015-05-061-0/+3
|/
* add channel_lastpost timestamp to help optimise some outrageously expensive ↵friendica2015-03-261-0/+2
| | | | queries.
* sql optimisation for affinity searches. A new index was added which wasn't ↵friendica2015-03-101-0/+1
| | | | 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-041-0/+2
|
* 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-241-0/+2
| | | | if the realm is so configured.
* provide relief to sites that are severely impacted by the slow ITEM_UNSEEN ↵friendica2015-02-121-0/+2
| | | | 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.
* two tracks proceeding in parallel - first adding the ability to store a ↵friendica2015-02-011-0/+1
| | | | 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.
* provide storage for directory based reputation in the xlink table by setting ↵friendica2015-01-261-0/+2
| | | | xlink_static = 1, so that xlink_static = 0 is traditional poco linkages
* add db update 1131/1132 to database schemaszottel2015-01-231-0/+2
|
* oauth permissions tablefriendica2015-01-191-0/+10
|
* PostgreSQL support initial commitHabeas Codice2014-11-131-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)
generated by cgit v1.2.3 (git 2.25.1) at 2024-12-14 16:37:07 +0000