| Age | Commit message (Collapse) | Author |
|---|
|
|
|
Some template specialization were not found, because they were not declared
at the point they were used.
We moved things around, things are less inter-dependant, and also now it
works.
|
|
|
|
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 #3305
|
|
|
|
|
|
|
|
fix #3317
|
|
fix #3336
|
|
Instead, generate a uuid for that message
|
|
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
|
|
Otherwise we can imagine that two clients changing this value at the same
time would mix things up.
ref #3275
|
|
fix #3275
|
|
This reverts commit ba879a882e031d7b8503f78fe41d1210000c96ca.
|
|
This reverts commit d62ca9f87906be6f046fe9d07afb8bfb69c166e3.
|
|
|
|
|
|
|
|
|
|
|
|
ref #3273
|
|
ref #3273
|
|
fix #3273
|
|
|
|
fix #3339
|
|
|
|
|
|
|
|
fix #3337
Because apparently the IDs are not always incrementing. We still use them to
know the order of two messages that were received at the same second (in
this case, the ID will always be incrementing).
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
