Age | Commit message (Collapse) | Author |
|
|
|
|
|
|
|
fix #3346
|
|
fix #3311
|
|
fix #3360
|
|
Also simplify how we did the whole “limit + 1”
And fix one bad interpretation of the XEP for the case where the query has
no after or before restriction.
fix #3349
|
|
This reverts commit 857c7d3972a03cbeebf730d99b924d3710dee6a0.
|
|
This reverts commit 5ef7ba08028065b03d51d1dc70bb35aeb41ae19d.
|
|
|
|
This way, it works, whatever the order of insertion in the database was.
fix #3343
|
|
|
|
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
|
|
|
|
fix #3305
|
|
fix #3305
|
|
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.”
|
|
fix #3283
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
fix #3325
|
|
|
|
These requests are only meant to be received by the room itself. The
participant must answer with not-implemented instead.
fix #3323
|
|
fix #3322
|
|
|
|
[skip-ci]
|
|
Supports the "seconds", "maxstanzas", "since" and "maxchars" (but only =0)
attributes.
fix #3270
|
|
Instead of irc.example.com@biboumi, because that’s actually user named
“irc.example.com”, in that case.
And that fixes the raw messages in fixed mode.
fix #3286
|
|
fix #3285
|
|
fix #3224
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
fix #3269
|
|
Entirely replace LiteSQL
fix #3271
|
|
fix #3250
|
|
fix #3219
|
|
fix #3256
|