| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | working through the xchan table to remove bitfields, mostly complete except ↵ | friendica | 2015-01-20 | 1 | -4/+3 |
| | | | | | for updating the updater | ||||
| * | PostgreSQL support initial commit | Habeas Codice | 2014-11-13 | 1 | -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) | ||||
| * | try and guess mimetype for openid profile photo | friendica | 2014-10-05 | 1 | -1/+3 |
| | | |||||
| * | fix third-party zid's | friendica | 2014-03-04 | 1 | -0/+2 |
| | | |||||
| * | minor stuff, some doco, auth cleanup, and make "unknown" more translateable ↵ | friendica | 2014-02-22 | 1 | -0/+1 |
| | | | | | by context. | ||||
| * | introduce a new privacy level "PERMS_AUTHED" to indicate somebody that is ↵ | friendica | 2014-02-18 | 1 | -8/+60 |
| | | | | | able to successfully authenticate (but is not necessarily in this network). | ||||
| * | some more snakebite and fix up include/account - forgot about that inline ↵ | friendica | 2014-02-18 | 1 | -14/+37 |
| | | | | | array stuff | ||||
| * | edit bookmarks | friendica | 2014-02-18 | 1 | -1/+1 |
| | | |||||
| * | remove the exit clause | friendica | 2014-02-17 | 1 | -6/+0 |
| | | |||||
| * | snakebite, cont. magic-auth via openid is now possible, with the caveat that ↵ | friendica | 2014-02-17 | 1 | -2/+20 |
| | | | | | one needs a hand-crafted xchan at the moment to make use of it and if you wish to do so, there will be no assistance or help provided. The risk of system instability and mangled DBs now and going forward is significant if you try this. | ||||
| * | operation snakebite continued. openid now works for local accounts using the ↵ | friendica | 2014-02-17 | 1 | -0/+101 |
| | | | | | rmagic module and after storing your openid in pconfig. This is just an interesting but trivial (in the bigger scheme of things) side effect of snakebite. The snake hasn't even waken up yet. | ||||
| * | trim a bit of fat | friendica | 2012-08-29 | 1 | -96/+0 |
| | | |||||
| * | Merge branch 'master' of https://github.com/friendica/friendica | Alexander Kampmann | 2012-04-05 | 1 | -0/+0 |
| | | | | | | | Conflicts: include/config.php update.php | ||||
| * | cleanup after openid refactoring | friendica | 2012-03-19 | 1 | -1/+6 |
| | | |||||
| * | refactor openid logins/registrations | friendica | 2012-03-19 | 1 | -51/+55 |
| | | |||||
| * | some openid fixes, use identity url from openid server and normalise it. | friendica | 2012-03-19 | 1 | -1/+8 |
| | | |||||
| * | add remove_user hook (it looks like dreamhost changed all my file ↵ | friendica | 2012-01-18 | 1 | -0/+0 |
| | | | | | permissions, this will make a nasty commit) | ||||
| * | modularise successful authentication | friendica | 2012-01-12 | 1 | -51/+5 |
| | | |||||
| * | account expiration structures | Friendika | 2011-09-18 | 1 | -1/+1 |
| | | |||||
| * | missing salmon key? report it. | Friendika | 2011-08-24 | 1 | -1/+2 |
| | | |||||
| * | some more zot changes migrating back to f9a mainline | Friendika | 2011-08-01 | 1 | -5/+5 |
| | | |||||
| * | Merge branch 'fabrixxm-master' | Friendika | 2011-05-23 | 1 | -4/+4 |
| |\ | | | | | | | | | Conflicts: boot.php | ||||
| | * | add info() function. Works like notice() but show messages in a div with ↵ | Fabio Comuni | 2011-05-23 | 1 | -4/+4 |
| | | | | | | | | | | | | | | | class info-message. update code to use info() instead of notice() when appropriate (non-error message) add info-message class style in themes | ||||
| * | | improved browser language detect, set user language on login | Friendika | 2011-05-23 | 1 | -1/+5 |
| |/ | |||||
| * | redirect to profile photo upload on very first login | Friendika | 2011-04-23 | 1 | -1/+10 |
| | | |||||
| * | update source strings | fabrixxm | 2011-03-11 | 1 | -1/+1 |
| | | |||||
| * | switch identities to manage pages | Friendika | 2011-03-01 | 1 | -2/+10 |
| | | |||||
| * | birthday notifications working | Friendika | 2011-01-13 | 1 | -1/+4 |
| | | |||||
| * | register/login timestamps | Friendika | 2010-12-16 | 1 | -0/+5 |
| | | |||||
| * | localise login template, allow openid to be disabled | Friendika | 2010-11-28 | 1 | -0/+4 |
| | | |||||
| * | use optional openid photo for registration - if supplied | Friendika | 2010-11-23 | 1 | -0/+9 |
| | | |||||
| * | openid registration | Friendika | 2010-11-17 | 1 | -0/+31 |
| | | |||||
| * | openid logins working | Friendika | 2010-11-17 | 1 | -0/+52 |
 |
index : volse-hubzilla.git | |
| Volse Hubzilla -- soft fork of main Hubzilla core for Volse | Harald Eilertsen |
| aboutsummaryrefslogtreecommitdiffstats |