summaryrefslogtreecommitdiff
AgeCommit message (Collapse)Author
2018-04-11Use a different Date data typelouiz’
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
2018-03-31Send the stanza-id for messages received by other userslouiz’
fix #3347
2018-03-26Fix the e2e test broken by previous commitlouiz’
2018-03-26Channel disco-info: use shorter stringGeorg Lukas
2018-03-23build:archlinux is way too slow, run it only manuallylouiz’
(that is, from time to time, hope I won’t forget)
2018-03-23Change the nick of the joining user AFTER sending all the join stufflouiz’
fix #3305
2018-03-23Properly handle force-join presences by sending everything in returnlouiz’
fix #3305
2018-03-23Check that db.prepare worked before using the returned statementlouiz’
2018-03-22Pass an IrcClient* to send_muc_leave instead of doing an other searchlouiz’
2018-03-19Add a missing pointer checklouiz’
2018-03-19Add a nick field in the IRC server configuration formlouiz’
fix #3317
2018-03-19Re-connect to postgresql when the connection is lostlouiz’
fix #3336
2018-03-18Update the changelog with this latest featurelouiz’
2018-03-18Don’t reflect an empty id if it was not includedlouiz’
Instead, generate a uuid for that message
2018-03-18Advertise the muc#stable_id feature on disco#info resultslouiz’
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.”
2018-03-18Reflect message IDs in channel MUCslouiz’
fix #3283
2018-03-18Add a multiline_message e2e testlouiz’
2018-03-18Use a transaction around the DELETE + INSERT of the after_connection_commandslouiz’
Otherwise we can imagine that two clients changing this value at the same time would mix things up. ref #3275
2018-03-18Add some missing includelouiz’
2018-03-18Allow the execution of multiple commands after the IRC connectionlouiz’
fix #3275
2018-03-18Use Catch2’s single_include/ directorylouiz’
2018-03-17Revert "C++17"louiz’
This reverts commit 3f088e7b3a1467a88e7c5ff9fb60dc4609d2bfa3.
2018-03-17Revert "Use std::optional<bool> instead of OptionalBool"louiz’
This reverts commit ba879a882e031d7b8503f78fe41d1210000c96ca.
2018-03-17Revert "Use if constexpr to make things a lot more readable"louiz’
This reverts commit d62ca9f87906be6f046fe9d07afb8bfb69c166e3.
2018-03-16Use if constexpr to make things a lot more readablelouiz’
2018-03-16Use std::optional<bool> instead of OptionalBoollouiz’
2018-03-16C++17louiz’
2018-03-15update docs to mention identd disable choiceAilin Nemui
2018-03-15follow coding styleAilin Nemui
2018-03-13optional identdAilin Nemui
2018-03-12Add a few \n in the e2e error messageslouiz’
2018-03-12Remove an unused functionlouiz’
2018-03-12Little doc typolouiz’
2018-03-12And this one (hostname -> address)louiz’
ref #3273
2018-03-12Rename a few “hostname” into “address”, regarding last commitlouiz’
ref #3273
2018-03-12Allow to override the addresses used to connect to an IRC networklouiz’
fix #3273
2018-03-12Fix the INSERT query for types that don’t have any Id columnlouiz’
2018-03-12Add a <item/> node in the presence of a leaving participantlouiz’
fix #3339
2018-03-12Remove the virtual channel feature altogetherlouiz’
2018-02-16Actually display the error message from postgresql when a query failedlouiz’
2018-02-16Log the warn/error messages coming from libpq in a correct formatlouiz’
2018-02-16Sort archive messages by date (and only then by id)louiz’
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).
2018-02-15Fix the actual_bind versions for integralslouiz’
2018-02-14Fix a memory leak when psql connection failslouiz’
2018-02-13Support the <before/> element in MAM requestslouiz’
2018-02-13Do not forget an early return, to return the correct item-not-found errorlouiz’
2018-02-13Use the same function for both history orderslouiz’
2018-02-11Fix a few warningslouiz’
2018-02-11Send a item-not-found error when the “after” value is not in the archivelouiz’
2018-02-10Handle the “after” RSM value to page through resultslouiz’