aboutsummaryrefslogtreecommitdiffstats
path: root/include/message.php
Commit message (Collapse)AuthorAgeFilesLines
* obscure mail subject in conversation structureredmatrix2015-09-011-1/+10
|
* private mail isuesredmatrix2015-08-091-2/+4
|
* more work on mail flagsredmatrix2015-06-231-10/+6
|
* add rot47 to the mix. This shouldn't affect the speed to any measurable degree.redmatrix2015-05-191-8/+8
|
* mail_obscure - AES-256 is way too slow, simplify. Ideally a substitution ↵redmatrix2015-05-191-12/+10
| | | | cipher would be adequate for our requirements.
* prevent silly fake null date from causing problems OTW from older buildsHabeas Codice2015-01-301-1/+1
|
* local_user => local_channelfriendica2015-01-281-4/+4
|
* PostgreSQL support initial commitHabeas Codice2014-11-131-4/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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)
* SQL error - private message conversation lookupfriendica2014-10-061-1/+1
|
* d* PM cont.friendica2014-09-231-2/+0
|
* more work on d* private messagesfriendica2014-09-231-2/+59
|
* 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'
* fix photos in private mailfriendica2014-02-271-1/+1
|
* Protocol: now set data['alg'] on all encapsulated encrypted packets, so that ↵friendica2013-11-201-8/+8
| | | | we can more easily retire 'aes256cbc' once it is no longer viable.
* E2EE on private mail (also fixed autocomplete results dropdown for recipient ↵friendica2013-11-131-2/+2
| | | | which was positioned below the navbar instead of next to the recipient input box)
* allow private mail sender to set an expiration on their messages. Once ↵friendica2013-11-061-4/+9
| | | | expired the message is destroyed at both ends (subject to the granularity of the polling interval) and is gone. Officially it takes some form of language independent string like 2013/11/22, but English speakers can use anything that strtotime() understands, like "+30 minutes" or "next Tuesday".
* email attachments (and fix email photos)friendica2013-08-191-2/+47
|
* convert all stored json calls to json_decode_plus()friendica2013-08-061-6/+6
|
* better mail obscuringfriendica2013-07-311-40/+54
|
* private mail is just a little more private now. Not encrypted and the ↵friendica2013-07-191-4/+20
| | | | | | obfuscation is easily reversible, but not casually readable by browsing logfiles or mysql dumps. This isn't backward compatible - folks will have to upgrade if they can't read their mail.
* rename 'uri' (and parent_uri) to 'mid' (and parent_mid) since these no ↵friendica2013-03-211-17/+17
| | | | longer remotely resemble uri's and are actually message_id's. This change is potentially destabilising because it touches a lot of code and structure. But it has to get done and there's no better time than the present.
* start formatting for Doxygenfriendica2013-02-251-1/+1
|
* null notice when sending private mailfriendica2013-02-041-2/+2
|
* upstream fixes, template regenerationfriendica2013-01-251-2/+5
|
* Putting the final wraps on the backend private message API. This is more or ↵friendica2013-01-251-19/+63
| | | | less what needs to happen for every data type and get all the SQL code out of the front-end controllers.
* make all private message functionality api-ablefriendica2013-01-241-1/+95
|
* turn private_messages_list into backend functionality and separate it from ↵friendica2013-01-241-0/+46
| | | | the controller
* DB: do the mail table again. Mail almost working onsite, still needs to zot ↵friendica2012-12-041-159/+29
| | | | though
* here's where the heavy lifting begins - everything is likely to be broken ↵friendica2012-10-011-1/+1
| | | | 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.
* item table rename parent-uri, target-type, object-type (more to come later)friendica2012-08-151-3/+3
|
* Merge branch 'master' of https://github.com/friendica/friendicaAlexander Kampmann2012-04-051-0/+85
|\ | | | | | | | | | | Conflicts: include/config.php update.php
| * send unverified private mail using zrlfriendica2012-04-011-0/+85
|/
* add remove_user hook (it looks like dreamhost changed all my file ↵friendica2012-01-181-0/+0
| | | | permissions, this will make a nasty commit)
* pm repliesfriendica2011-12-061-7/+15
|
* d* pmfriendica2011-12-061-3/+9
|
* maintain backward compatibility with old PMsfriendica2011-12-051-9/+19
|
* add conv structurefriendica2011-12-051-3/+40
|
* move send private message code out of view codefabrixxm2011-08-191-0/+96
generated by cgit v1.2.3 (git 2.25.1) at 2024-12-28 07:19:03 +0000