- 02 May, 2018 2 commits
- 30 Apr, 2018 1 commit
-
-
louiz’ authored
fix #3351 See https://github.com/randombit/botan/issues/1558
-
- 29 Apr, 2018 3 commits
- 28 Apr, 2018 4 commits
- 24 Apr, 2018 3 commits
-
- 15 Apr, 2018 5 commits
-
-
Link Mauve authored
-
Link Mauve authored
-
Link Mauve authored
-
Link Mauve authored
-
Link Mauve authored
-
- 14 Apr, 2018 1 commit
-
-
louiz’ authored
This way, it works, whatever the order of insertion in the database was. fix #3343
-
- 13 Apr, 2018 3 commits
- 10 Apr, 2018 2 commits
-
-
louiz’ authored
-
louiz’ authored
PLEASE backup your database before testing this commit, and report any migration issue. In postgresql, we use timestamp with timezone. In sqlite3 we use REAL (the date is expressed as julianday) This requires a migration of the muclogline_ table: In postgresql it’s pretty simple, we convert all the integer into timestamps With sqlite3, we actually rename the table, create the new one with the correct type, then copy everything to the new table, with a conversion function for the Date_ column, and then we delete the old table. fix #3343
-
- 31 Mar, 2018 1 commit
-
- 26 Mar, 2018 2 commits
- 23 Mar, 2018 4 commits
- 22 Mar, 2018 1 commit
-
-
louiz’ authored
-
- 19 Mar, 2018 2 commits
-
-
louiz’ authored
-
- 18 Mar, 2018 6 commits
-
-
louiz’ authored
-
louiz’ authored
Instead, generate a uuid for that message
-
louiz’ authored
From XEP 0045: “Note: the requirement to reflect the 'id' attribute was added in version 1.31 of this XEP. Servers following the new specification SHOULD advertise that with a disco info feature of 'http://jabber.org/protocol/muc#stable_id' on both the service domain and on individual MUCs, so that clients can check for support.”
-
louiz’ authored