Age | Commit message (Collapse) | Author |
|
|
|
|
|
|
|
fix #3362
|
|
fix #3346
|
|
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 #3347
|
|
fix #3305
|
|
|
|
fix #3317
|
|
Instead, generate a uuid for that message
|
|
fix #3283
|
|
fix #3339
|
|
|
|
|
|
|
|
See https://xmpp.org/extensions/xep-0045.html#privatemessage
fix #3321
|
|
|
|
|
|
|
|
|
|
fix #3293
|
|
fix #3284
|
|
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 #3277
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Entirely replace LiteSQL
fix #3271
|
|
|
|
|
|
|
|
This reverts commit 5d801ddcd025f68d2ec91edf0462091a32c779c1.
|
|
on it"
This reverts commit 45f7396c8d30ed37570c4ecdaa886388f9beba3e.
|
|
fix #3243
|
|
fix #3259
|
|
fix #3254
|
|
|
|
|
|
fix #3252
|