2019-11-21 16:19:22 +00:00
package protocol
2019-08-06 21:50:13 +00:00
import (
2019-08-20 11:20:25 +00:00
"context"
2019-08-06 21:50:13 +00:00
"database/sql"
Move to protobuf for Message type (#1706)
* Use a single Message type `v1/message.go` and `message.go` are the same now, and they embed `protobuf.ChatMessage`
* Use `SendChatMessage` for sending chat messages, this is basically the old `Send` but a bit more flexible so we can send different message types (stickers,commands), and not just text.
* Remove dedup from services/shhext. Because now we process in status-protocol, dedup makes less sense, as those messages are going to be processed anyway, so removing for now, we can re-evaluate if bringing it to status-go or not.
* Change the various retrieveX method to a single one:
`RetrieveAll` will be processing those messages that it can process (Currently only `Message`), and return the rest in `RawMessages` (still transit). The format for the response is:
`Chats`: -> The chats updated by receiving the message
`Messages`: -> The messages retrieved (already matched to a chat)
`Contacts`: -> The contacts updated by the messages
`RawMessages` -> Anything else that can't be parsed, eventually as we move everything to status-protocol-go this will go away.
2019-12-05 16:25:34 +00:00
"encoding/json"
2019-08-06 21:50:13 +00:00
"fmt"
"strings"
2020-09-01 13:27:01 +00:00
"github.com/status-im/status-go/protocol/common"
2020-01-02 09:10:19 +00:00
"github.com/status-im/status-go/protocol/protobuf"
2019-08-06 21:50:13 +00:00
)
2020-05-20 12:16:12 +00:00
func ( db sqlitePersistence ) tableUserMessagesAllFields ( ) string {
2019-08-06 21:50:13 +00:00
return ` id ,
whisper_timestamp ,
source ,
Move to protobuf for Message type (#1706)
* Use a single Message type `v1/message.go` and `message.go` are the same now, and they embed `protobuf.ChatMessage`
* Use `SendChatMessage` for sending chat messages, this is basically the old `Send` but a bit more flexible so we can send different message types (stickers,commands), and not just text.
* Remove dedup from services/shhext. Because now we process in status-protocol, dedup makes less sense, as those messages are going to be processed anyway, so removing for now, we can re-evaluate if bringing it to status-go or not.
* Change the various retrieveX method to a single one:
`RetrieveAll` will be processing those messages that it can process (Currently only `Message`), and return the rest in `RawMessages` (still transit). The format for the response is:
`Chats`: -> The chats updated by receiving the message
`Messages`: -> The messages retrieved (already matched to a chat)
`Contacts`: -> The contacts updated by the messages
`RawMessages` -> Anything else that can't be parsed, eventually as we move everything to status-protocol-go this will go away.
2019-12-05 16:25:34 +00:00
text ,
2019-08-06 21:50:13 +00:00
content_type ,
username ,
timestamp ,
chat_id ,
Move to protobuf for Message type (#1706)
* Use a single Message type `v1/message.go` and `message.go` are the same now, and they embed `protobuf.ChatMessage`
* Use `SendChatMessage` for sending chat messages, this is basically the old `Send` but a bit more flexible so we can send different message types (stickers,commands), and not just text.
* Remove dedup from services/shhext. Because now we process in status-protocol, dedup makes less sense, as those messages are going to be processed anyway, so removing for now, we can re-evaluate if bringing it to status-go or not.
* Change the various retrieveX method to a single one:
`RetrieveAll` will be processing those messages that it can process (Currently only `Message`), and return the rest in `RawMessages` (still transit). The format for the response is:
`Chats`: -> The chats updated by receiving the message
`Messages`: -> The messages retrieved (already matched to a chat)
`Contacts`: -> The contacts updated by the messages
`RawMessages` -> Anything else that can't be parsed, eventually as we move everything to status-protocol-go this will go away.
2019-12-05 16:25:34 +00:00
local_chat_id ,
2019-08-06 21:50:13 +00:00
message_type ,
clock_value ,
seen ,
2019-08-20 11:20:25 +00:00
outgoing_status ,
Move to protobuf for Message type (#1706)
* Use a single Message type `v1/message.go` and `message.go` are the same now, and they embed `protobuf.ChatMessage`
* Use `SendChatMessage` for sending chat messages, this is basically the old `Send` but a bit more flexible so we can send different message types (stickers,commands), and not just text.
* Remove dedup from services/shhext. Because now we process in status-protocol, dedup makes less sense, as those messages are going to be processed anyway, so removing for now, we can re-evaluate if bringing it to status-go or not.
* Change the various retrieveX method to a single one:
`RetrieveAll` will be processing those messages that it can process (Currently only `Message`), and return the rest in `RawMessages` (still transit). The format for the response is:
`Chats`: -> The chats updated by receiving the message
`Messages`: -> The messages retrieved (already matched to a chat)
`Contacts`: -> The contacts updated by the messages
`RawMessages` -> Anything else that can't be parsed, eventually as we move everything to status-protocol-go this will go away.
2019-12-05 16:25:34 +00:00
parsed_text ,
sticker_pack ,
sticker_hash ,
2020-05-13 13:16:17 +00:00
image_payload ,
image_type ,
image_base64 ,
2020-06-17 18:55:49 +00:00
audio_payload ,
audio_type ,
2020-06-23 14:30:39 +00:00
audio_duration_ms ,
2020-06-17 18:55:49 +00:00
audio_base64 ,
2020-11-18 09:16:51 +00:00
community_id ,
2020-09-01 10:34:28 +00:00
mentions ,
2020-10-27 17:35:28 +00:00
links ,
2020-01-10 18:59:01 +00:00
command_id ,
command_value ,
command_from ,
command_address ,
command_contract ,
command_transaction_hash ,
command_state ,
command_signature ,
Add replies to messages
Currently replies to messages are handled in status-react.
This causes some issues with the fact that sometimes replies might come
out of order, they might be offloaded to the database etc.
This commit changes the behavior so that status-go always returns the
replies, and in case a reply comes out of order (first the reply, later
the message being replied to), it will include in the messages the
updated message.
It also adds some fields (RTL,Replace,LineCount) to the database which
were not previously saved, resulting in some potential bugs.
The method that we use to pull replies is currently a bit naive, we just
pull all the message again from the database, but has the advantage of
being simple. It will go through performance testing to make sure
performnace are acceptable, if so I think it's reasonable to avoid some
complexity.
2020-04-08 13:42:02 +00:00
replace_message ,
2021-06-07 08:31:27 +00:00
edited_at ,
Add replies to messages
Currently replies to messages are handled in status-react.
This causes some issues with the fact that sometimes replies might come
out of order, they might be offloaded to the database etc.
This commit changes the behavior so that status-go always returns the
replies, and in case a reply comes out of order (first the reply, later
the message being replied to), it will include in the messages the
updated message.
It also adds some fields (RTL,Replace,LineCount) to the database which
were not previously saved, resulting in some potential bugs.
The method that we use to pull replies is currently a bit naive, we just
pull all the message again from the database, but has the advantage of
being simple. It will go through performance testing to make sure
performnace are acceptable, if so I think it's reasonable to avoid some
complexity.
2020-04-08 13:42:02 +00:00
rtl ,
line_count ,
2021-03-25 15:15:22 +00:00
response_to ,
gap_from ,
2021-05-25 09:40:02 +00:00
gap_to ,
mentioned `
2019-08-20 11:20:25 +00:00
}
2020-05-20 12:16:12 +00:00
func ( db sqlitePersistence ) tableUserMessagesAllFieldsJoin ( ) string {
2019-08-20 11:20:25 +00:00
return ` m1 . id ,
m1 . whisper_timestamp ,
m1 . source ,
Move to protobuf for Message type (#1706)
* Use a single Message type `v1/message.go` and `message.go` are the same now, and they embed `protobuf.ChatMessage`
* Use `SendChatMessage` for sending chat messages, this is basically the old `Send` but a bit more flexible so we can send different message types (stickers,commands), and not just text.
* Remove dedup from services/shhext. Because now we process in status-protocol, dedup makes less sense, as those messages are going to be processed anyway, so removing for now, we can re-evaluate if bringing it to status-go or not.
* Change the various retrieveX method to a single one:
`RetrieveAll` will be processing those messages that it can process (Currently only `Message`), and return the rest in `RawMessages` (still transit). The format for the response is:
`Chats`: -> The chats updated by receiving the message
`Messages`: -> The messages retrieved (already matched to a chat)
`Contacts`: -> The contacts updated by the messages
`RawMessages` -> Anything else that can't be parsed, eventually as we move everything to status-protocol-go this will go away.
2019-12-05 16:25:34 +00:00
m1 . text ,
2019-08-20 11:20:25 +00:00
m1 . content_type ,
m1 . username ,
m1 . timestamp ,
m1 . chat_id ,
Move to protobuf for Message type (#1706)
* Use a single Message type `v1/message.go` and `message.go` are the same now, and they embed `protobuf.ChatMessage`
* Use `SendChatMessage` for sending chat messages, this is basically the old `Send` but a bit more flexible so we can send different message types (stickers,commands), and not just text.
* Remove dedup from services/shhext. Because now we process in status-protocol, dedup makes less sense, as those messages are going to be processed anyway, so removing for now, we can re-evaluate if bringing it to status-go or not.
* Change the various retrieveX method to a single one:
`RetrieveAll` will be processing those messages that it can process (Currently only `Message`), and return the rest in `RawMessages` (still transit). The format for the response is:
`Chats`: -> The chats updated by receiving the message
`Messages`: -> The messages retrieved (already matched to a chat)
`Contacts`: -> The contacts updated by the messages
`RawMessages` -> Anything else that can't be parsed, eventually as we move everything to status-protocol-go this will go away.
2019-12-05 16:25:34 +00:00
m1 . local_chat_id ,
2019-08-20 11:20:25 +00:00
m1 . message_type ,
m1 . clock_value ,
m1 . seen ,
m1 . outgoing_status ,
Move to protobuf for Message type (#1706)
* Use a single Message type `v1/message.go` and `message.go` are the same now, and they embed `protobuf.ChatMessage`
* Use `SendChatMessage` for sending chat messages, this is basically the old `Send` but a bit more flexible so we can send different message types (stickers,commands), and not just text.
* Remove dedup from services/shhext. Because now we process in status-protocol, dedup makes less sense, as those messages are going to be processed anyway, so removing for now, we can re-evaluate if bringing it to status-go or not.
* Change the various retrieveX method to a single one:
`RetrieveAll` will be processing those messages that it can process (Currently only `Message`), and return the rest in `RawMessages` (still transit). The format for the response is:
`Chats`: -> The chats updated by receiving the message
`Messages`: -> The messages retrieved (already matched to a chat)
`Contacts`: -> The contacts updated by the messages
`RawMessages` -> Anything else that can't be parsed, eventually as we move everything to status-protocol-go this will go away.
2019-12-05 16:25:34 +00:00
m1 . parsed_text ,
m1 . sticker_pack ,
m1 . sticker_hash ,
2020-05-13 13:16:17 +00:00
m1 . image_base64 ,
2020-07-30 06:26:19 +00:00
COALESCE ( m1 . audio_duration_ms , 0 ) ,
2020-06-17 18:55:49 +00:00
m1 . audio_base64 ,
2020-11-18 09:16:51 +00:00
m1 . community_id ,
2020-09-01 10:34:28 +00:00
m1 . mentions ,
2020-10-27 17:35:28 +00:00
m1 . links ,
2020-01-10 18:59:01 +00:00
m1 . command_id ,
m1 . command_value ,
m1 . command_from ,
m1 . command_address ,
m1 . command_contract ,
m1 . command_transaction_hash ,
m1 . command_state ,
m1 . command_signature ,
Add replies to messages
Currently replies to messages are handled in status-react.
This causes some issues with the fact that sometimes replies might come
out of order, they might be offloaded to the database etc.
This commit changes the behavior so that status-go always returns the
replies, and in case a reply comes out of order (first the reply, later
the message being replied to), it will include in the messages the
updated message.
It also adds some fields (RTL,Replace,LineCount) to the database which
were not previously saved, resulting in some potential bugs.
The method that we use to pull replies is currently a bit naive, we just
pull all the message again from the database, but has the advantage of
being simple. It will go through performance testing to make sure
performnace are acceptable, if so I think it's reasonable to avoid some
complexity.
2020-04-08 13:42:02 +00:00
m1 . replace_message ,
2021-06-07 08:31:27 +00:00
m1 . edited_at ,
Add replies to messages
Currently replies to messages are handled in status-react.
This causes some issues with the fact that sometimes replies might come
out of order, they might be offloaded to the database etc.
This commit changes the behavior so that status-go always returns the
replies, and in case a reply comes out of order (first the reply, later
the message being replied to), it will include in the messages the
updated message.
It also adds some fields (RTL,Replace,LineCount) to the database which
were not previously saved, resulting in some potential bugs.
The method that we use to pull replies is currently a bit naive, we just
pull all the message again from the database, but has the advantage of
being simple. It will go through performance testing to make sure
performnace are acceptable, if so I think it's reasonable to avoid some
complexity.
2020-04-08 13:42:02 +00:00
m1 . rtl ,
m1 . line_count ,
Move to protobuf for Message type (#1706)
* Use a single Message type `v1/message.go` and `message.go` are the same now, and they embed `protobuf.ChatMessage`
* Use `SendChatMessage` for sending chat messages, this is basically the old `Send` but a bit more flexible so we can send different message types (stickers,commands), and not just text.
* Remove dedup from services/shhext. Because now we process in status-protocol, dedup makes less sense, as those messages are going to be processed anyway, so removing for now, we can re-evaluate if bringing it to status-go or not.
* Change the various retrieveX method to a single one:
`RetrieveAll` will be processing those messages that it can process (Currently only `Message`), and return the rest in `RawMessages` (still transit). The format for the response is:
`Chats`: -> The chats updated by receiving the message
`Messages`: -> The messages retrieved (already matched to a chat)
`Contacts`: -> The contacts updated by the messages
`RawMessages` -> Anything else that can't be parsed, eventually as we move everything to status-protocol-go this will go away.
2019-12-05 16:25:34 +00:00
m1 . response_to ,
2021-03-25 15:15:22 +00:00
m1 . gap_from ,
m1 . gap_to ,
2021-05-25 09:40:02 +00:00
m1 . mentioned ,
2019-08-20 11:20:25 +00:00
m2 . source ,
Move to protobuf for Message type (#1706)
* Use a single Message type `v1/message.go` and `message.go` are the same now, and they embed `protobuf.ChatMessage`
* Use `SendChatMessage` for sending chat messages, this is basically the old `Send` but a bit more flexible so we can send different message types (stickers,commands), and not just text.
* Remove dedup from services/shhext. Because now we process in status-protocol, dedup makes less sense, as those messages are going to be processed anyway, so removing for now, we can re-evaluate if bringing it to status-go or not.
* Change the various retrieveX method to a single one:
`RetrieveAll` will be processing those messages that it can process (Currently only `Message`), and return the rest in `RawMessages` (still transit). The format for the response is:
`Chats`: -> The chats updated by receiving the message
`Messages`: -> The messages retrieved (already matched to a chat)
`Contacts`: -> The contacts updated by the messages
`RawMessages` -> Anything else that can't be parsed, eventually as we move everything to status-protocol-go this will go away.
2019-12-05 16:25:34 +00:00
m2 . text ,
2020-09-09 11:03:29 +00:00
m2 . parsed_text ,
2020-05-14 05:40:40 +00:00
m2 . image_base64 ,
2020-06-23 14:30:39 +00:00
m2 . audio_duration_ms ,
2020-06-17 18:55:49 +00:00
m2 . audio_base64 ,
2020-11-18 09:16:51 +00:00
m2 . community_id ,
2019-09-26 07:01:17 +00:00
c . alias ,
c . identicon `
2019-08-06 21:50:13 +00:00
}
2020-05-20 12:16:12 +00:00
func ( db sqlitePersistence ) tableUserMessagesAllFieldsCount ( ) int {
return strings . Count ( db . tableUserMessagesAllFields ( ) , "," ) + 1
2019-08-06 21:50:13 +00:00
}
type scanner interface {
Scan ( dest ... interface { } ) error
}
2020-09-01 13:27:01 +00:00
func ( db sqlitePersistence ) tableUserMessagesScanAllFields ( row scanner , message * common . Message , others ... interface { } ) error {
Move to protobuf for Message type (#1706)
* Use a single Message type `v1/message.go` and `message.go` are the same now, and they embed `protobuf.ChatMessage`
* Use `SendChatMessage` for sending chat messages, this is basically the old `Send` but a bit more flexible so we can send different message types (stickers,commands), and not just text.
* Remove dedup from services/shhext. Because now we process in status-protocol, dedup makes less sense, as those messages are going to be processed anyway, so removing for now, we can re-evaluate if bringing it to status-go or not.
* Change the various retrieveX method to a single one:
`RetrieveAll` will be processing those messages that it can process (Currently only `Message`), and return the rest in `RawMessages` (still transit). The format for the response is:
`Chats`: -> The chats updated by receiving the message
`Messages`: -> The messages retrieved (already matched to a chat)
`Contacts`: -> The contacts updated by the messages
`RawMessages` -> Anything else that can't be parsed, eventually as we move everything to status-protocol-go this will go away.
2019-12-05 16:25:34 +00:00
var quotedText sql . NullString
2020-09-09 11:03:29 +00:00
var quotedParsedText [ ] byte
2019-08-20 11:20:25 +00:00
var quotedFrom sql . NullString
2020-05-14 05:40:40 +00:00
var quotedImage sql . NullString
2020-06-17 18:55:49 +00:00
var quotedAudio sql . NullString
2020-06-23 14:30:39 +00:00
var quotedAudioDuration sql . NullInt64
2020-11-18 09:16:51 +00:00
var quotedCommunityID sql . NullString
2020-09-01 10:34:28 +00:00
var serializedMentions [ ] byte
2020-10-27 17:35:28 +00:00
var serializedLinks [ ] byte
2019-09-26 07:01:17 +00:00
var alias sql . NullString
var identicon sql . NullString
2021-01-07 11:16:19 +00:00
var communityID sql . NullString
2021-03-25 15:15:22 +00:00
var gapFrom sql . NullInt64
var gapTo sql . NullInt64
2021-06-07 08:31:27 +00:00
var editedAt sql . NullInt64
Move to protobuf for Message type (#1706)
* Use a single Message type `v1/message.go` and `message.go` are the same now, and they embed `protobuf.ChatMessage`
* Use `SendChatMessage` for sending chat messages, this is basically the old `Send` but a bit more flexible so we can send different message types (stickers,commands), and not just text.
* Remove dedup from services/shhext. Because now we process in status-protocol, dedup makes less sense, as those messages are going to be processed anyway, so removing for now, we can re-evaluate if bringing it to status-go or not.
* Change the various retrieveX method to a single one:
`RetrieveAll` will be processing those messages that it can process (Currently only `Message`), and return the rest in `RawMessages` (still transit). The format for the response is:
`Chats`: -> The chats updated by receiving the message
`Messages`: -> The messages retrieved (already matched to a chat)
`Contacts`: -> The contacts updated by the messages
`RawMessages` -> Anything else that can't be parsed, eventually as we move everything to status-protocol-go this will go away.
2019-12-05 16:25:34 +00:00
sticker := & protobuf . StickerMessage { }
2020-09-01 13:27:01 +00:00
command := & common . CommandParameters { }
2020-06-23 14:30:39 +00:00
audio := & protobuf . AudioMessage { }
Move to protobuf for Message type (#1706)
* Use a single Message type `v1/message.go` and `message.go` are the same now, and they embed `protobuf.ChatMessage`
* Use `SendChatMessage` for sending chat messages, this is basically the old `Send` but a bit more flexible so we can send different message types (stickers,commands), and not just text.
* Remove dedup from services/shhext. Because now we process in status-protocol, dedup makes less sense, as those messages are going to be processed anyway, so removing for now, we can re-evaluate if bringing it to status-go or not.
* Change the various retrieveX method to a single one:
`RetrieveAll` will be processing those messages that it can process (Currently only `Message`), and return the rest in `RawMessages` (still transit). The format for the response is:
`Chats`: -> The chats updated by receiving the message
`Messages`: -> The messages retrieved (already matched to a chat)
`Contacts`: -> The contacts updated by the messages
`RawMessages` -> Anything else that can't be parsed, eventually as we move everything to status-protocol-go this will go away.
2019-12-05 16:25:34 +00:00
2019-08-06 21:50:13 +00:00
args := [ ] interface { } {
& message . ID ,
& message . WhisperTimestamp ,
& message . From , // source in table
Move to protobuf for Message type (#1706)
* Use a single Message type `v1/message.go` and `message.go` are the same now, and they embed `protobuf.ChatMessage`
* Use `SendChatMessage` for sending chat messages, this is basically the old `Send` but a bit more flexible so we can send different message types (stickers,commands), and not just text.
* Remove dedup from services/shhext. Because now we process in status-protocol, dedup makes less sense, as those messages are going to be processed anyway, so removing for now, we can re-evaluate if bringing it to status-go or not.
* Change the various retrieveX method to a single one:
`RetrieveAll` will be processing those messages that it can process (Currently only `Message`), and return the rest in `RawMessages` (still transit). The format for the response is:
`Chats`: -> The chats updated by receiving the message
`Messages`: -> The messages retrieved (already matched to a chat)
`Contacts`: -> The contacts updated by the messages
`RawMessages` -> Anything else that can't be parsed, eventually as we move everything to status-protocol-go this will go away.
2019-12-05 16:25:34 +00:00
& message . Text ,
2019-08-06 21:50:13 +00:00
& message . ContentType ,
2019-09-26 07:01:17 +00:00
& message . Alias ,
2019-08-06 21:50:13 +00:00
& message . Timestamp ,
Move to protobuf for Message type (#1706)
* Use a single Message type `v1/message.go` and `message.go` are the same now, and they embed `protobuf.ChatMessage`
* Use `SendChatMessage` for sending chat messages, this is basically the old `Send` but a bit more flexible so we can send different message types (stickers,commands), and not just text.
* Remove dedup from services/shhext. Because now we process in status-protocol, dedup makes less sense, as those messages are going to be processed anyway, so removing for now, we can re-evaluate if bringing it to status-go or not.
* Change the various retrieveX method to a single one:
`RetrieveAll` will be processing those messages that it can process (Currently only `Message`), and return the rest in `RawMessages` (still transit). The format for the response is:
`Chats`: -> The chats updated by receiving the message
`Messages`: -> The messages retrieved (already matched to a chat)
`Contacts`: -> The contacts updated by the messages
`RawMessages` -> Anything else that can't be parsed, eventually as we move everything to status-protocol-go this will go away.
2019-12-05 16:25:34 +00:00
& message . ChatId ,
& message . LocalChatID ,
2019-08-06 21:50:13 +00:00
& message . MessageType ,
Move to protobuf for Message type (#1706)
* Use a single Message type `v1/message.go` and `message.go` are the same now, and they embed `protobuf.ChatMessage`
* Use `SendChatMessage` for sending chat messages, this is basically the old `Send` but a bit more flexible so we can send different message types (stickers,commands), and not just text.
* Remove dedup from services/shhext. Because now we process in status-protocol, dedup makes less sense, as those messages are going to be processed anyway, so removing for now, we can re-evaluate if bringing it to status-go or not.
* Change the various retrieveX method to a single one:
`RetrieveAll` will be processing those messages that it can process (Currently only `Message`), and return the rest in `RawMessages` (still transit). The format for the response is:
`Chats`: -> The chats updated by receiving the message
`Messages`: -> The messages retrieved (already matched to a chat)
`Contacts`: -> The contacts updated by the messages
`RawMessages` -> Anything else that can't be parsed, eventually as we move everything to status-protocol-go this will go away.
2019-12-05 16:25:34 +00:00
& message . Clock ,
2019-08-06 21:50:13 +00:00
& message . Seen ,
& message . OutgoingStatus ,
Move to protobuf for Message type (#1706)
* Use a single Message type `v1/message.go` and `message.go` are the same now, and they embed `protobuf.ChatMessage`
* Use `SendChatMessage` for sending chat messages, this is basically the old `Send` but a bit more flexible so we can send different message types (stickers,commands), and not just text.
* Remove dedup from services/shhext. Because now we process in status-protocol, dedup makes less sense, as those messages are going to be processed anyway, so removing for now, we can re-evaluate if bringing it to status-go or not.
* Change the various retrieveX method to a single one:
`RetrieveAll` will be processing those messages that it can process (Currently only `Message`), and return the rest in `RawMessages` (still transit). The format for the response is:
`Chats`: -> The chats updated by receiving the message
`Messages`: -> The messages retrieved (already matched to a chat)
`Contacts`: -> The contacts updated by the messages
`RawMessages` -> Anything else that can't be parsed, eventually as we move everything to status-protocol-go this will go away.
2019-12-05 16:25:34 +00:00
& message . ParsedText ,
& sticker . Pack ,
& sticker . Hash ,
2020-05-13 13:16:17 +00:00
& message . Base64Image ,
2020-06-23 14:30:39 +00:00
& audio . DurationMs ,
2020-06-17 18:55:49 +00:00
& message . Base64Audio ,
2021-01-07 11:16:19 +00:00
& communityID ,
2020-09-01 10:34:28 +00:00
& serializedMentions ,
2020-10-27 17:35:28 +00:00
& serializedLinks ,
2020-01-10 18:59:01 +00:00
& command . ID ,
& command . Value ,
& command . From ,
& command . Address ,
& command . Contract ,
& command . TransactionHash ,
& command . CommandState ,
& command . Signature ,
Add replies to messages
Currently replies to messages are handled in status-react.
This causes some issues with the fact that sometimes replies might come
out of order, they might be offloaded to the database etc.
This commit changes the behavior so that status-go always returns the
replies, and in case a reply comes out of order (first the reply, later
the message being replied to), it will include in the messages the
updated message.
It also adds some fields (RTL,Replace,LineCount) to the database which
were not previously saved, resulting in some potential bugs.
The method that we use to pull replies is currently a bit naive, we just
pull all the message again from the database, but has the advantage of
being simple. It will go through performance testing to make sure
performnace are acceptable, if so I think it's reasonable to avoid some
complexity.
2020-04-08 13:42:02 +00:00
& message . Replace ,
2021-06-07 08:31:27 +00:00
& editedAt ,
Add replies to messages
Currently replies to messages are handled in status-react.
This causes some issues with the fact that sometimes replies might come
out of order, they might be offloaded to the database etc.
This commit changes the behavior so that status-go always returns the
replies, and in case a reply comes out of order (first the reply, later
the message being replied to), it will include in the messages the
updated message.
It also adds some fields (RTL,Replace,LineCount) to the database which
were not previously saved, resulting in some potential bugs.
The method that we use to pull replies is currently a bit naive, we just
pull all the message again from the database, but has the advantage of
being simple. It will go through performance testing to make sure
performnace are acceptable, if so I think it's reasonable to avoid some
complexity.
2020-04-08 13:42:02 +00:00
& message . RTL ,
& message . LineCount ,
Move to protobuf for Message type (#1706)
* Use a single Message type `v1/message.go` and `message.go` are the same now, and they embed `protobuf.ChatMessage`
* Use `SendChatMessage` for sending chat messages, this is basically the old `Send` but a bit more flexible so we can send different message types (stickers,commands), and not just text.
* Remove dedup from services/shhext. Because now we process in status-protocol, dedup makes less sense, as those messages are going to be processed anyway, so removing for now, we can re-evaluate if bringing it to status-go or not.
* Change the various retrieveX method to a single one:
`RetrieveAll` will be processing those messages that it can process (Currently only `Message`), and return the rest in `RawMessages` (still transit). The format for the response is:
`Chats`: -> The chats updated by receiving the message
`Messages`: -> The messages retrieved (already matched to a chat)
`Contacts`: -> The contacts updated by the messages
`RawMessages` -> Anything else that can't be parsed, eventually as we move everything to status-protocol-go this will go away.
2019-12-05 16:25:34 +00:00
& message . ResponseTo ,
2021-03-25 15:15:22 +00:00
& gapFrom ,
& gapTo ,
2021-05-25 09:40:02 +00:00
& message . Mentioned ,
2019-08-20 11:20:25 +00:00
& quotedFrom ,
Move to protobuf for Message type (#1706)
* Use a single Message type `v1/message.go` and `message.go` are the same now, and they embed `protobuf.ChatMessage`
* Use `SendChatMessage` for sending chat messages, this is basically the old `Send` but a bit more flexible so we can send different message types (stickers,commands), and not just text.
* Remove dedup from services/shhext. Because now we process in status-protocol, dedup makes less sense, as those messages are going to be processed anyway, so removing for now, we can re-evaluate if bringing it to status-go or not.
* Change the various retrieveX method to a single one:
`RetrieveAll` will be processing those messages that it can process (Currently only `Message`), and return the rest in `RawMessages` (still transit). The format for the response is:
`Chats`: -> The chats updated by receiving the message
`Messages`: -> The messages retrieved (already matched to a chat)
`Contacts`: -> The contacts updated by the messages
`RawMessages` -> Anything else that can't be parsed, eventually as we move everything to status-protocol-go this will go away.
2019-12-05 16:25:34 +00:00
& quotedText ,
2020-09-09 11:03:29 +00:00
& quotedParsedText ,
2020-05-14 05:40:40 +00:00
& quotedImage ,
2020-06-23 14:30:39 +00:00
& quotedAudioDuration ,
2020-06-17 18:55:49 +00:00
& quotedAudio ,
2020-11-18 09:16:51 +00:00
& quotedCommunityID ,
2019-09-26 07:01:17 +00:00
& alias ,
& identicon ,
2019-08-20 11:20:25 +00:00
}
err := row . Scan ( append ( args , others ... ) ... )
if err != nil {
return err
}
2021-06-07 08:31:27 +00:00
if editedAt . Valid {
message . EditedAt = uint64 ( editedAt . Int64 )
2021-06-03 13:11:55 +00:00
}
Move to protobuf for Message type (#1706)
* Use a single Message type `v1/message.go` and `message.go` are the same now, and they embed `protobuf.ChatMessage`
* Use `SendChatMessage` for sending chat messages, this is basically the old `Send` but a bit more flexible so we can send different message types (stickers,commands), and not just text.
* Remove dedup from services/shhext. Because now we process in status-protocol, dedup makes less sense, as those messages are going to be processed anyway, so removing for now, we can re-evaluate if bringing it to status-go or not.
* Change the various retrieveX method to a single one:
`RetrieveAll` will be processing those messages that it can process (Currently only `Message`), and return the rest in `RawMessages` (still transit). The format for the response is:
`Chats`: -> The chats updated by receiving the message
`Messages`: -> The messages retrieved (already matched to a chat)
`Contacts`: -> The contacts updated by the messages
`RawMessages` -> Anything else that can't be parsed, eventually as we move everything to status-protocol-go this will go away.
2019-12-05 16:25:34 +00:00
if quotedText . Valid {
2020-09-01 13:27:01 +00:00
message . QuotedMessage = & common . QuotedMessage {
2020-06-23 14:30:39 +00:00
From : quotedFrom . String ,
Text : quotedText . String ,
2020-09-09 11:03:29 +00:00
ParsedText : quotedParsedText ,
2020-06-23 14:30:39 +00:00
Base64Image : quotedImage . String ,
AudioDurationMs : uint64 ( quotedAudioDuration . Int64 ) ,
Base64Audio : quotedAudio . String ,
2020-11-18 09:16:51 +00:00
CommunityID : quotedCommunityID . String ,
2019-08-20 11:20:25 +00:00
}
2019-08-06 21:50:13 +00:00
}
2019-09-26 07:01:17 +00:00
message . Alias = alias . String
message . Identicon = identicon . String
2020-07-10 14:18:01 +00:00
2021-03-25 15:15:22 +00:00
if gapFrom . Valid && gapTo . Valid {
message . GapParameters = & common . GapParameters {
From : uint32 ( gapFrom . Int64 ) ,
To : uint32 ( gapTo . Int64 ) ,
}
}
2021-01-07 11:16:19 +00:00
if communityID . Valid {
message . CommunityID = communityID . String
}
2020-09-01 10:34:28 +00:00
if serializedMentions != nil {
err := json . Unmarshal ( serializedMentions , & message . Mentions )
if err != nil {
return err
}
}
2020-10-27 17:35:28 +00:00
if serializedLinks != nil {
err := json . Unmarshal ( serializedLinks , & message . Links )
if err != nil {
return err
}
}
2020-07-10 14:20:18 +00:00
switch message . ContentType {
case protobuf . ChatMessage_STICKER :
Move to protobuf for Message type (#1706)
* Use a single Message type `v1/message.go` and `message.go` are the same now, and they embed `protobuf.ChatMessage`
* Use `SendChatMessage` for sending chat messages, this is basically the old `Send` but a bit more flexible so we can send different message types (stickers,commands), and not just text.
* Remove dedup from services/shhext. Because now we process in status-protocol, dedup makes less sense, as those messages are going to be processed anyway, so removing for now, we can re-evaluate if bringing it to status-go or not.
* Change the various retrieveX method to a single one:
`RetrieveAll` will be processing those messages that it can process (Currently only `Message`), and return the rest in `RawMessages` (still transit). The format for the response is:
`Chats`: -> The chats updated by receiving the message
`Messages`: -> The messages retrieved (already matched to a chat)
`Contacts`: -> The contacts updated by the messages
`RawMessages` -> Anything else that can't be parsed, eventually as we move everything to status-protocol-go this will go away.
2019-12-05 16:25:34 +00:00
message . Payload = & protobuf . ChatMessage_Sticker { Sticker : sticker }
2019-09-26 07:01:17 +00:00
2020-08-13 17:57:17 +00:00
case protobuf . ChatMessage_AUDIO :
message . Payload = & protobuf . ChatMessage_Audio { Audio : audio }
2020-06-23 14:30:39 +00:00
2020-07-10 14:20:18 +00:00
case protobuf . ChatMessage_TRANSACTION_COMMAND :
2020-01-10 18:59:01 +00:00
message . CommandParameters = command
}
2019-08-20 11:20:25 +00:00
return nil
2019-08-06 21:50:13 +00:00
}
2020-09-01 13:27:01 +00:00
func ( db sqlitePersistence ) tableUserMessagesAllValues ( message * common . Message ) ( [ ] interface { } , error ) {
2021-03-25 15:15:22 +00:00
var gapFrom , gapTo uint32
Move to protobuf for Message type (#1706)
* Use a single Message type `v1/message.go` and `message.go` are the same now, and they embed `protobuf.ChatMessage`
* Use `SendChatMessage` for sending chat messages, this is basically the old `Send` but a bit more flexible so we can send different message types (stickers,commands), and not just text.
* Remove dedup from services/shhext. Because now we process in status-protocol, dedup makes less sense, as those messages are going to be processed anyway, so removing for now, we can re-evaluate if bringing it to status-go or not.
* Change the various retrieveX method to a single one:
`RetrieveAll` will be processing those messages that it can process (Currently only `Message`), and return the rest in `RawMessages` (still transit). The format for the response is:
`Chats`: -> The chats updated by receiving the message
`Messages`: -> The messages retrieved (already matched to a chat)
`Contacts`: -> The contacts updated by the messages
`RawMessages` -> Anything else that can't be parsed, eventually as we move everything to status-protocol-go this will go away.
2019-12-05 16:25:34 +00:00
sticker := message . GetSticker ( )
if sticker == nil {
sticker = & protobuf . StickerMessage { }
}
2020-05-13 13:16:17 +00:00
image := message . GetImage ( )
if image == nil {
image = & protobuf . ImageMessage { }
}
2020-06-17 18:55:49 +00:00
audio := message . GetAudio ( )
if audio == nil {
audio = & protobuf . AudioMessage { }
}
2020-01-10 18:59:01 +00:00
command := message . CommandParameters
if command == nil {
2020-09-01 13:27:01 +00:00
command = & common . CommandParameters { }
2020-01-10 18:59:01 +00:00
}
2020-09-01 10:34:28 +00:00
2021-03-25 15:15:22 +00:00
if message . GapParameters != nil {
gapFrom = message . GapParameters . From
gapTo = message . GapParameters . To
}
2020-09-01 10:34:28 +00:00
var serializedMentions [ ] byte
var err error
if len ( message . Mentions ) != 0 {
serializedMentions , err = json . Marshal ( message . Mentions )
if err != nil {
return nil , err
}
}
2020-10-27 17:35:28 +00:00
var serializedLinks [ ] byte
if len ( message . Links ) != 0 {
serializedLinks , err = json . Marshal ( message . Links )
if err != nil {
return nil , err
}
}
2019-08-06 21:50:13 +00:00
return [ ] interface { } {
message . ID ,
message . WhisperTimestamp ,
message . From , // source in table
Move to protobuf for Message type (#1706)
* Use a single Message type `v1/message.go` and `message.go` are the same now, and they embed `protobuf.ChatMessage`
* Use `SendChatMessage` for sending chat messages, this is basically the old `Send` but a bit more flexible so we can send different message types (stickers,commands), and not just text.
* Remove dedup from services/shhext. Because now we process in status-protocol, dedup makes less sense, as those messages are going to be processed anyway, so removing for now, we can re-evaluate if bringing it to status-go or not.
* Change the various retrieveX method to a single one:
`RetrieveAll` will be processing those messages that it can process (Currently only `Message`), and return the rest in `RawMessages` (still transit). The format for the response is:
`Chats`: -> The chats updated by receiving the message
`Messages`: -> The messages retrieved (already matched to a chat)
`Contacts`: -> The contacts updated by the messages
`RawMessages` -> Anything else that can't be parsed, eventually as we move everything to status-protocol-go this will go away.
2019-12-05 16:25:34 +00:00
message . Text ,
2019-08-06 21:50:13 +00:00
message . ContentType ,
2019-09-26 07:01:17 +00:00
message . Alias ,
2019-08-06 21:50:13 +00:00
message . Timestamp ,
Move to protobuf for Message type (#1706)
* Use a single Message type `v1/message.go` and `message.go` are the same now, and they embed `protobuf.ChatMessage`
* Use `SendChatMessage` for sending chat messages, this is basically the old `Send` but a bit more flexible so we can send different message types (stickers,commands), and not just text.
* Remove dedup from services/shhext. Because now we process in status-protocol, dedup makes less sense, as those messages are going to be processed anyway, so removing for now, we can re-evaluate if bringing it to status-go or not.
* Change the various retrieveX method to a single one:
`RetrieveAll` will be processing those messages that it can process (Currently only `Message`), and return the rest in `RawMessages` (still transit). The format for the response is:
`Chats`: -> The chats updated by receiving the message
`Messages`: -> The messages retrieved (already matched to a chat)
`Contacts`: -> The contacts updated by the messages
`RawMessages` -> Anything else that can't be parsed, eventually as we move everything to status-protocol-go this will go away.
2019-12-05 16:25:34 +00:00
message . ChatId ,
message . LocalChatID ,
2019-08-06 21:50:13 +00:00
message . MessageType ,
Move to protobuf for Message type (#1706)
* Use a single Message type `v1/message.go` and `message.go` are the same now, and they embed `protobuf.ChatMessage`
* Use `SendChatMessage` for sending chat messages, this is basically the old `Send` but a bit more flexible so we can send different message types (stickers,commands), and not just text.
* Remove dedup from services/shhext. Because now we process in status-protocol, dedup makes less sense, as those messages are going to be processed anyway, so removing for now, we can re-evaluate if bringing it to status-go or not.
* Change the various retrieveX method to a single one:
`RetrieveAll` will be processing those messages that it can process (Currently only `Message`), and return the rest in `RawMessages` (still transit). The format for the response is:
`Chats`: -> The chats updated by receiving the message
`Messages`: -> The messages retrieved (already matched to a chat)
`Contacts`: -> The contacts updated by the messages
`RawMessages` -> Anything else that can't be parsed, eventually as we move everything to status-protocol-go this will go away.
2019-12-05 16:25:34 +00:00
message . Clock ,
2019-08-06 21:50:13 +00:00
message . Seen ,
message . OutgoingStatus ,
Move to protobuf for Message type (#1706)
* Use a single Message type `v1/message.go` and `message.go` are the same now, and they embed `protobuf.ChatMessage`
* Use `SendChatMessage` for sending chat messages, this is basically the old `Send` but a bit more flexible so we can send different message types (stickers,commands), and not just text.
* Remove dedup from services/shhext. Because now we process in status-protocol, dedup makes less sense, as those messages are going to be processed anyway, so removing for now, we can re-evaluate if bringing it to status-go or not.
* Change the various retrieveX method to a single one:
`RetrieveAll` will be processing those messages that it can process (Currently only `Message`), and return the rest in `RawMessages` (still transit). The format for the response is:
`Chats`: -> The chats updated by receiving the message
`Messages`: -> The messages retrieved (already matched to a chat)
`Contacts`: -> The contacts updated by the messages
`RawMessages` -> Anything else that can't be parsed, eventually as we move everything to status-protocol-go this will go away.
2019-12-05 16:25:34 +00:00
message . ParsedText ,
sticker . Pack ,
sticker . Hash ,
2020-05-13 13:16:17 +00:00
image . Payload ,
image . Type ,
message . Base64Image ,
2020-06-17 18:55:49 +00:00
audio . Payload ,
audio . Type ,
2020-06-23 14:30:39 +00:00
audio . DurationMs ,
2020-06-17 18:55:49 +00:00
message . Base64Audio ,
2020-11-18 09:16:51 +00:00
message . CommunityID ,
2020-09-01 10:34:28 +00:00
serializedMentions ,
2020-10-27 17:35:28 +00:00
serializedLinks ,
2020-01-10 18:59:01 +00:00
command . ID ,
command . Value ,
command . From ,
command . Address ,
command . Contract ,
command . TransactionHash ,
command . CommandState ,
command . Signature ,
Add replies to messages
Currently replies to messages are handled in status-react.
This causes some issues with the fact that sometimes replies might come
out of order, they might be offloaded to the database etc.
This commit changes the behavior so that status-go always returns the
replies, and in case a reply comes out of order (first the reply, later
the message being replied to), it will include in the messages the
updated message.
It also adds some fields (RTL,Replace,LineCount) to the database which
were not previously saved, resulting in some potential bugs.
The method that we use to pull replies is currently a bit naive, we just
pull all the message again from the database, but has the advantage of
being simple. It will go through performance testing to make sure
performnace are acceptable, if so I think it's reasonable to avoid some
complexity.
2020-04-08 13:42:02 +00:00
message . Replace ,
2021-06-07 11:45:06 +00:00
int64 ( message . EditedAt ) ,
Add replies to messages
Currently replies to messages are handled in status-react.
This causes some issues with the fact that sometimes replies might come
out of order, they might be offloaded to the database etc.
This commit changes the behavior so that status-go always returns the
replies, and in case a reply comes out of order (first the reply, later
the message being replied to), it will include in the messages the
updated message.
It also adds some fields (RTL,Replace,LineCount) to the database which
were not previously saved, resulting in some potential bugs.
The method that we use to pull replies is currently a bit naive, we just
pull all the message again from the database, but has the advantage of
being simple. It will go through performance testing to make sure
performnace are acceptable, if so I think it's reasonable to avoid some
complexity.
2020-04-08 13:42:02 +00:00
message . RTL ,
message . LineCount ,
Move to protobuf for Message type (#1706)
* Use a single Message type `v1/message.go` and `message.go` are the same now, and they embed `protobuf.ChatMessage`
* Use `SendChatMessage` for sending chat messages, this is basically the old `Send` but a bit more flexible so we can send different message types (stickers,commands), and not just text.
* Remove dedup from services/shhext. Because now we process in status-protocol, dedup makes less sense, as those messages are going to be processed anyway, so removing for now, we can re-evaluate if bringing it to status-go or not.
* Change the various retrieveX method to a single one:
`RetrieveAll` will be processing those messages that it can process (Currently only `Message`), and return the rest in `RawMessages` (still transit). The format for the response is:
`Chats`: -> The chats updated by receiving the message
`Messages`: -> The messages retrieved (already matched to a chat)
`Contacts`: -> The contacts updated by the messages
`RawMessages` -> Anything else that can't be parsed, eventually as we move everything to status-protocol-go this will go away.
2019-12-05 16:25:34 +00:00
message . ResponseTo ,
2021-03-25 15:15:22 +00:00
gapFrom ,
gapTo ,
2021-05-25 09:40:02 +00:00
message . Mentioned ,
Move to protobuf for Message type (#1706)
* Use a single Message type `v1/message.go` and `message.go` are the same now, and they embed `protobuf.ChatMessage`
* Use `SendChatMessage` for sending chat messages, this is basically the old `Send` but a bit more flexible so we can send different message types (stickers,commands), and not just text.
* Remove dedup from services/shhext. Because now we process in status-protocol, dedup makes less sense, as those messages are going to be processed anyway, so removing for now, we can re-evaluate if bringing it to status-go or not.
* Change the various retrieveX method to a single one:
`RetrieveAll` will be processing those messages that it can process (Currently only `Message`), and return the rest in `RawMessages` (still transit). The format for the response is:
`Chats`: -> The chats updated by receiving the message
`Messages`: -> The messages retrieved (already matched to a chat)
`Contacts`: -> The contacts updated by the messages
`RawMessages` -> Anything else that can't be parsed, eventually as we move everything to status-protocol-go this will go away.
2019-12-05 16:25:34 +00:00
} , nil
2019-08-06 21:50:13 +00:00
}
2020-09-01 13:27:01 +00:00
func ( db sqlitePersistence ) messageByID ( tx * sql . Tx , id string ) ( * common . Message , error ) {
Move to protobuf for Message type (#1706)
* Use a single Message type `v1/message.go` and `message.go` are the same now, and they embed `protobuf.ChatMessage`
* Use `SendChatMessage` for sending chat messages, this is basically the old `Send` but a bit more flexible so we can send different message types (stickers,commands), and not just text.
* Remove dedup from services/shhext. Because now we process in status-protocol, dedup makes less sense, as those messages are going to be processed anyway, so removing for now, we can re-evaluate if bringing it to status-go or not.
* Change the various retrieveX method to a single one:
`RetrieveAll` will be processing those messages that it can process (Currently only `Message`), and return the rest in `RawMessages` (still transit). The format for the response is:
`Chats`: -> The chats updated by receiving the message
`Messages`: -> The messages retrieved (already matched to a chat)
`Contacts`: -> The contacts updated by the messages
`RawMessages` -> Anything else that can't be parsed, eventually as we move everything to status-protocol-go this will go away.
2019-12-05 16:25:34 +00:00
var err error
if tx == nil {
tx , err = db . db . BeginTx ( context . Background ( ) , & sql . TxOptions { } )
if err != nil {
return nil , err
}
defer func ( ) {
if err == nil {
err = tx . Commit ( )
return
}
// don't shadow original error
_ = tx . Rollback ( )
} ( )
}
2020-09-01 13:27:01 +00:00
var message common . Message
2019-08-06 21:50:13 +00:00
2020-05-20 12:16:12 +00:00
allFields := db . tableUserMessagesAllFieldsJoin ( )
Move to protobuf for Message type (#1706)
* Use a single Message type `v1/message.go` and `message.go` are the same now, and they embed `protobuf.ChatMessage`
* Use `SendChatMessage` for sending chat messages, this is basically the old `Send` but a bit more flexible so we can send different message types (stickers,commands), and not just text.
* Remove dedup from services/shhext. Because now we process in status-protocol, dedup makes less sense, as those messages are going to be processed anyway, so removing for now, we can re-evaluate if bringing it to status-go or not.
* Change the various retrieveX method to a single one:
`RetrieveAll` will be processing those messages that it can process (Currently only `Message`), and return the rest in `RawMessages` (still transit). The format for the response is:
`Chats`: -> The chats updated by receiving the message
`Messages`: -> The messages retrieved (already matched to a chat)
`Contacts`: -> The contacts updated by the messages
`RawMessages` -> Anything else that can't be parsed, eventually as we move everything to status-protocol-go this will go away.
2019-12-05 16:25:34 +00:00
row := tx . QueryRow (
2019-08-06 21:50:13 +00:00
fmt . Sprintf ( `
SELECT
% s
FROM
2020-01-10 18:59:01 +00:00
user_messages m1
2019-08-20 11:20:25 +00:00
LEFT JOIN
2020-01-10 18:59:01 +00:00
user_messages m2
2019-08-20 11:20:25 +00:00
ON
Move to protobuf for Message type (#1706)
* Use a single Message type `v1/message.go` and `message.go` are the same now, and they embed `protobuf.ChatMessage`
* Use `SendChatMessage` for sending chat messages, this is basically the old `Send` but a bit more flexible so we can send different message types (stickers,commands), and not just text.
* Remove dedup from services/shhext. Because now we process in status-protocol, dedup makes less sense, as those messages are going to be processed anyway, so removing for now, we can re-evaluate if bringing it to status-go or not.
* Change the various retrieveX method to a single one:
`RetrieveAll` will be processing those messages that it can process (Currently only `Message`), and return the rest in `RawMessages` (still transit). The format for the response is:
`Chats`: -> The chats updated by receiving the message
`Messages`: -> The messages retrieved (already matched to a chat)
`Contacts`: -> The contacts updated by the messages
`RawMessages` -> Anything else that can't be parsed, eventually as we move everything to status-protocol-go this will go away.
2019-12-05 16:25:34 +00:00
m1 . response_to = m2 . id
2019-09-26 07:01:17 +00:00
LEFT JOIN
contacts c
ON
m1 . source = c . id
2019-08-06 21:50:13 +00:00
WHERE
2019-08-20 11:20:25 +00:00
m1 . id = ?
2019-08-06 21:50:13 +00:00
` , allFields ) ,
id ,
)
2020-05-20 12:16:12 +00:00
err = db . tableUserMessagesScanAllFields ( row , & message )
2019-08-06 21:50:13 +00:00
switch err {
case sql . ErrNoRows :
2020-10-08 10:46:03 +00:00
return nil , common . ErrRecordNotFound
2019-08-06 21:50:13 +00:00
case nil :
return & message , nil
default :
return nil , err
}
}
2020-09-01 13:27:01 +00:00
func ( db sqlitePersistence ) MessageByCommandID ( chatID , id string ) ( * common . Message , error ) {
2020-01-10 18:59:01 +00:00
2020-09-01 13:27:01 +00:00
var message common . Message
2020-01-10 18:59:01 +00:00
2020-05-20 12:16:12 +00:00
allFields := db . tableUserMessagesAllFieldsJoin ( )
2020-01-10 18:59:01 +00:00
row := db . db . QueryRow (
fmt . Sprintf ( `
SELECT
% s
FROM
user_messages m1
LEFT JOIN
user_messages m2
ON
m1 . response_to = m2 . id
LEFT JOIN
contacts c
ON
m1 . source = c . id
WHERE
m1 . command_id = ?
2020-01-17 12:39:09 +00:00
AND
m1 . local_chat_id = ?
2020-01-10 18:59:01 +00:00
ORDER BY m1 . clock_value DESC
LIMIT 1
` , allFields ) ,
id ,
2020-01-17 12:39:09 +00:00
chatID ,
2020-01-10 18:59:01 +00:00
)
2020-05-20 12:16:12 +00:00
err := db . tableUserMessagesScanAllFields ( row , & message )
2020-01-10 18:59:01 +00:00
switch err {
case sql . ErrNoRows :
2020-10-08 10:46:03 +00:00
return nil , common . ErrRecordNotFound
2020-01-10 18:59:01 +00:00
case nil :
return & message , nil
default :
return nil , err
}
}
2020-09-01 13:27:01 +00:00
func ( db sqlitePersistence ) MessageByID ( id string ) ( * common . Message , error ) {
Move to protobuf for Message type (#1706)
* Use a single Message type `v1/message.go` and `message.go` are the same now, and they embed `protobuf.ChatMessage`
* Use `SendChatMessage` for sending chat messages, this is basically the old `Send` but a bit more flexible so we can send different message types (stickers,commands), and not just text.
* Remove dedup from services/shhext. Because now we process in status-protocol, dedup makes less sense, as those messages are going to be processed anyway, so removing for now, we can re-evaluate if bringing it to status-go or not.
* Change the various retrieveX method to a single one:
`RetrieveAll` will be processing those messages that it can process (Currently only `Message`), and return the rest in `RawMessages` (still transit). The format for the response is:
`Chats`: -> The chats updated by receiving the message
`Messages`: -> The messages retrieved (already matched to a chat)
`Contacts`: -> The contacts updated by the messages
`RawMessages` -> Anything else that can't be parsed, eventually as we move everything to status-protocol-go this will go away.
2019-12-05 16:25:34 +00:00
return db . messageByID ( nil , id )
}
2019-08-20 11:20:25 +00:00
func ( db sqlitePersistence ) MessagesExist ( ids [ ] string ) ( map [ string ] bool , error ) {
result := make ( map [ string ] bool )
if len ( ids ) == 0 {
2019-08-06 21:50:13 +00:00
return result , nil
}
2019-08-20 11:20:25 +00:00
idsArgs := make ( [ ] interface { } , 0 , len ( ids ) )
for _ , id := range ids {
idsArgs = append ( idsArgs , id )
}
inVector := strings . Repeat ( "?, " , len ( ids ) - 1 ) + "?"
2020-02-10 11:22:37 +00:00
query := "SELECT id FROM user_messages WHERE id IN (" + inVector + ")" // nolint: gosec
2019-08-20 11:20:25 +00:00
rows , err := db . db . Query ( query , idsArgs ... )
if err != nil {
return nil , err
}
defer rows . Close ( )
for rows . Next ( ) {
var id string
err := rows . Scan ( & id )
if err != nil {
return nil , err
}
result [ id ] = true
}
return result , nil
2019-08-06 21:50:13 +00:00
}
2020-09-01 13:27:01 +00:00
func ( db sqlitePersistence ) MessagesByIDs ( ids [ ] string ) ( [ ] * common . Message , error ) {
Add replies to messages
Currently replies to messages are handled in status-react.
This causes some issues with the fact that sometimes replies might come
out of order, they might be offloaded to the database etc.
This commit changes the behavior so that status-go always returns the
replies, and in case a reply comes out of order (first the reply, later
the message being replied to), it will include in the messages the
updated message.
It also adds some fields (RTL,Replace,LineCount) to the database which
were not previously saved, resulting in some potential bugs.
The method that we use to pull replies is currently a bit naive, we just
pull all the message again from the database, but has the advantage of
being simple. It will go through performance testing to make sure
performnace are acceptable, if so I think it's reasonable to avoid some
complexity.
2020-04-08 13:42:02 +00:00
if len ( ids ) == 0 {
return nil , nil
}
idsArgs := make ( [ ] interface { } , 0 , len ( ids ) )
for _ , id := range ids {
idsArgs = append ( idsArgs , id )
}
2020-05-20 12:16:12 +00:00
allFields := db . tableUserMessagesAllFieldsJoin ( )
Add replies to messages
Currently replies to messages are handled in status-react.
This causes some issues with the fact that sometimes replies might come
out of order, they might be offloaded to the database etc.
This commit changes the behavior so that status-go always returns the
replies, and in case a reply comes out of order (first the reply, later
the message being replied to), it will include in the messages the
updated message.
It also adds some fields (RTL,Replace,LineCount) to the database which
were not previously saved, resulting in some potential bugs.
The method that we use to pull replies is currently a bit naive, we just
pull all the message again from the database, but has the advantage of
being simple. It will go through performance testing to make sure
performnace are acceptable, if so I think it's reasonable to avoid some
complexity.
2020-04-08 13:42:02 +00:00
inVector := strings . Repeat ( "?, " , len ( ids ) - 1 ) + "?"
// nolint: gosec
rows , err := db . db . Query ( fmt . Sprintf ( `
SELECT
% s
FROM
user_messages m1
LEFT JOIN
user_messages m2
ON
m1 . response_to = m2 . id
LEFT JOIN
contacts c
ON
m1 . source = c . id
2020-06-04 10:11:37 +00:00
WHERE NOT ( m1 . hide ) AND m1 . id IN ( % s ) ` , allFields , inVector ) , idsArgs ... )
Add replies to messages
Currently replies to messages are handled in status-react.
This causes some issues with the fact that sometimes replies might come
out of order, they might be offloaded to the database etc.
This commit changes the behavior so that status-go always returns the
replies, and in case a reply comes out of order (first the reply, later
the message being replied to), it will include in the messages the
updated message.
It also adds some fields (RTL,Replace,LineCount) to the database which
were not previously saved, resulting in some potential bugs.
The method that we use to pull replies is currently a bit naive, we just
pull all the message again from the database, but has the advantage of
being simple. It will go through performance testing to make sure
performnace are acceptable, if so I think it's reasonable to avoid some
complexity.
2020-04-08 13:42:02 +00:00
if err != nil {
return nil , err
}
defer rows . Close ( )
2020-07-28 07:53:32 +00:00
2020-09-01 13:27:01 +00:00
var result [ ] * common . Message
Add replies to messages
Currently replies to messages are handled in status-react.
This causes some issues with the fact that sometimes replies might come
out of order, they might be offloaded to the database etc.
This commit changes the behavior so that status-go always returns the
replies, and in case a reply comes out of order (first the reply, later
the message being replied to), it will include in the messages the
updated message.
It also adds some fields (RTL,Replace,LineCount) to the database which
were not previously saved, resulting in some potential bugs.
The method that we use to pull replies is currently a bit naive, we just
pull all the message again from the database, but has the advantage of
being simple. It will go through performance testing to make sure
performnace are acceptable, if so I think it's reasonable to avoid some
complexity.
2020-04-08 13:42:02 +00:00
for rows . Next ( ) {
2020-09-01 13:27:01 +00:00
var message common . Message
2020-05-20 12:16:12 +00:00
if err := db . tableUserMessagesScanAllFields ( rows , & message ) ; err != nil {
Add replies to messages
Currently replies to messages are handled in status-react.
This causes some issues with the fact that sometimes replies might come
out of order, they might be offloaded to the database etc.
This commit changes the behavior so that status-go always returns the
replies, and in case a reply comes out of order (first the reply, later
the message being replied to), it will include in the messages the
updated message.
It also adds some fields (RTL,Replace,LineCount) to the database which
were not previously saved, resulting in some potential bugs.
The method that we use to pull replies is currently a bit naive, we just
pull all the message again from the database, but has the advantage of
being simple. It will go through performance testing to make sure
performnace are acceptable, if so I think it's reasonable to avoid some
complexity.
2020-04-08 13:42:02 +00:00
return nil , err
}
result = append ( result , & message )
}
return result , nil
}
2019-08-06 21:50:13 +00:00
// MessageByChatID returns all messages for a given chatID in descending order.
// Ordering is accomplished using two concatenated values: ClockValue and ID.
// These two values are also used to compose a cursor which is returned to the result.
2020-09-01 13:27:01 +00:00
func ( db sqlitePersistence ) MessageByChatID ( chatID string , currCursor string , limit int ) ( [ ] * common . Message , string , error ) {
2019-08-06 21:50:13 +00:00
cursorWhere := ""
if currCursor != "" {
2020-11-05 16:07:24 +00:00
cursorWhere = "AND cursor <= ?" //nolint: goconst
2019-08-06 21:50:13 +00:00
}
2020-05-20 12:16:12 +00:00
allFields := db . tableUserMessagesAllFieldsJoin ( )
2019-08-06 21:50:13 +00:00
args := [ ] interface { } { chatID }
if currCursor != "" {
args = append ( args , currCursor )
}
// Build a new column `cursor` at the query time by having a fixed-sized clock value at the beginning
2019-09-26 07:01:17 +00:00
// concatenated with message ID. Results are sorted using this new column.
2019-08-06 21:50:13 +00:00
// This new column values can also be returned as a cursor for subsequent requests.
rows , err := db . db . Query (
fmt . Sprintf ( `
SELECT
% s ,
2019-08-20 11:20:25 +00:00
substr ( ' 0000000000000000000000000000000000000000000000000000000000000000 ' || m1 . clock_value , - 64 , 64 ) || m1 . id as cursor
2019-08-06 21:50:13 +00:00
FROM
2020-01-10 18:59:01 +00:00
user_messages m1
2019-08-20 11:20:25 +00:00
LEFT JOIN
2020-01-10 18:59:01 +00:00
user_messages m2
2019-08-20 11:20:25 +00:00
ON
Move to protobuf for Message type (#1706)
* Use a single Message type `v1/message.go` and `message.go` are the same now, and they embed `protobuf.ChatMessage`
* Use `SendChatMessage` for sending chat messages, this is basically the old `Send` but a bit more flexible so we can send different message types (stickers,commands), and not just text.
* Remove dedup from services/shhext. Because now we process in status-protocol, dedup makes less sense, as those messages are going to be processed anyway, so removing for now, we can re-evaluate if bringing it to status-go or not.
* Change the various retrieveX method to a single one:
`RetrieveAll` will be processing those messages that it can process (Currently only `Message`), and return the rest in `RawMessages` (still transit). The format for the response is:
`Chats`: -> The chats updated by receiving the message
`Messages`: -> The messages retrieved (already matched to a chat)
`Contacts`: -> The contacts updated by the messages
`RawMessages` -> Anything else that can't be parsed, eventually as we move everything to status-protocol-go this will go away.
2019-12-05 16:25:34 +00:00
m1 . response_to = m2 . id
2019-09-26 07:01:17 +00:00
LEFT JOIN
contacts c
ON
m1 . source = c . id
2019-08-06 21:50:13 +00:00
WHERE
2020-06-04 10:11:37 +00:00
NOT ( m1 . hide ) AND m1 . local_chat_id = ? % s
2019-08-06 21:50:13 +00:00
ORDER BY cursor DESC
LIMIT ?
` , allFields , cursorWhere ) ,
append ( args , limit + 1 ) ... , // take one more to figure our whether a cursor should be returned
)
if err != nil {
return nil , "" , err
}
defer rows . Close ( )
var (
2020-09-01 13:27:01 +00:00
result [ ] * common . Message
2019-08-06 21:50:13 +00:00
cursors [ ] string
)
for rows . Next ( ) {
var (
2020-09-01 13:27:01 +00:00
message common . Message
2019-08-06 21:50:13 +00:00
cursor string
)
2020-05-20 12:16:12 +00:00
if err := db . tableUserMessagesScanAllFields ( rows , & message , & cursor ) ; err != nil {
2019-08-06 21:50:13 +00:00
return nil , "" , err
}
result = append ( result , & message )
cursors = append ( cursors , cursor )
}
var newCursor string
if len ( result ) > limit {
newCursor = cursors [ limit ]
result = result [ : limit ]
}
return result , newCursor , nil
}
2021-05-14 21:22:50 +00:00
// PinnedMessageByChatID returns all pinned messages for a given chatID in descending order.
// Ordering is accomplished using two concatenated values: ClockValue and ID.
// These two values are also used to compose a cursor which is returned to the result.
func ( db sqlitePersistence ) PinnedMessageByChatIDs ( chatIDs [ ] string , currCursor string , limit int ) ( [ ] * common . PinnedMessage , string , error ) {
cursorWhere := ""
if currCursor != "" {
cursorWhere = "AND cursor <= ?" //nolint: goconst
}
allFields := db . tableUserMessagesAllFieldsJoin ( )
args := make ( [ ] interface { } , len ( chatIDs ) )
for i , v := range chatIDs {
args [ i ] = v
}
if currCursor != "" {
args = append ( args , currCursor )
}
// Build a new column `cursor` at the query time by having a fixed-sized clock value at the beginning
// concatenated with message ID. Results are sorted using this new column.
// This new column values can also be returned as a cursor for subsequent requests.
rows , err := db . db . Query (
fmt . Sprintf ( `
SELECT
% s ,
pm . clock_value as pinnedAt ,
2021-06-08 15:23:32 +00:00
pm . pinned_by as pinnedBy ,
2021-05-14 21:22:50 +00:00
substr ( ' 0000000000000000000000000000000000000000000000000000000000000000 ' || m1 . clock_value , - 64 , 64 ) || m1 . id as cursor
FROM
pin_messages pm
JOIN
user_messages m1
ON
pm . message_id = m1 . id
LEFT JOIN
user_messages m2
ON
m1 . response_to = m2 . id
LEFT JOIN
contacts c
ON
m1 . source = c . id
WHERE
pm . pinned = 1
AND NOT ( m1 . hide ) AND m1 . local_chat_id IN % s % s
ORDER BY cursor DESC
LIMIT ?
` , allFields , "(?" + strings . Repeat ( ",?" , len ( chatIDs ) - 1 ) + ")" , cursorWhere ) ,
append ( args , limit + 1 ) ... , // take one more to figure our whether a cursor should be returned
)
if err != nil {
return nil , "" , err
}
defer rows . Close ( )
var (
result [ ] * common . PinnedMessage
cursors [ ] string
)
for rows . Next ( ) {
var (
message common . Message
pinnedAt uint64
2021-06-08 15:23:32 +00:00
pinnedBy string
2021-05-14 21:22:50 +00:00
cursor string
)
2021-06-08 15:23:32 +00:00
if err := db . tableUserMessagesScanAllFields ( rows , & message , & pinnedAt , & pinnedBy , & cursor ) ; err != nil {
2021-05-14 21:22:50 +00:00
return nil , "" , err
}
pinnedMessage := & common . PinnedMessage {
2021-06-08 15:23:32 +00:00
Message : & message ,
2021-05-14 21:22:50 +00:00
PinnedAt : pinnedAt ,
2021-06-08 15:23:32 +00:00
PinnedBy : pinnedBy ,
2021-05-14 21:22:50 +00:00
}
result = append ( result , pinnedMessage )
cursors = append ( cursors , cursor )
}
var newCursor string
if len ( result ) > limit && cursors != nil {
newCursor = cursors [ limit ]
result = result [ : limit ]
}
return result , newCursor , nil
}
func ( db sqlitePersistence ) PinnedMessageByChatID ( chatID string , currCursor string , limit int ) ( [ ] * common . PinnedMessage , string , error ) {
return db . PinnedMessageByChatIDs ( [ ] string { chatID } , currCursor , limit )
}
2020-11-03 10:16:05 +00:00
// MessageByChatIDs returns all messages for a given chatIDs in descending order.
// Ordering is accomplished using two concatenated values: ClockValue and ID.
// These two values are also used to compose a cursor which is returned to the result.
func ( db sqlitePersistence ) MessageByChatIDs ( chatIDs [ ] string , currCursor string , limit int ) ( [ ] * common . Message , string , error ) {
cursorWhere := ""
if currCursor != "" {
2020-11-05 16:07:24 +00:00
cursorWhere = "AND cursor <= ?" //nolint: goconst
2020-11-03 10:16:05 +00:00
}
allFields := db . tableUserMessagesAllFieldsJoin ( )
args := make ( [ ] interface { } , len ( chatIDs ) )
for i , v := range chatIDs {
args [ i ] = v
}
if currCursor != "" {
args = append ( args , currCursor )
}
// Build a new column `cursor` at the query time by having a fixed-sized clock value at the beginning
// concatenated with message ID. Results are sorted using this new column.
// This new column values can also be returned as a cursor for subsequent requests.
rows , err := db . db . Query (
fmt . Sprintf ( `
SELECT
% s ,
substr ( ' 0000000000000000000000000000000000000000000000000000000000000000 ' || m1 . clock_value , - 64 , 64 ) || m1 . id as cursor
FROM
user_messages m1
LEFT JOIN
user_messages m2
ON
m1 . response_to = m2 . id
LEFT JOIN
contacts c
ON
m1 . source = c . id
WHERE
NOT ( m1 . hide ) AND m1 . local_chat_id IN % s % s
ORDER BY cursor DESC
LIMIT ?
` , allFields , "(?" + strings . Repeat ( ",?" , len ( chatIDs ) - 1 ) + ")" , cursorWhere ) ,
append ( args , limit + 1 ) ... , // take one more to figure our whether a cursor should be returned
)
if err != nil {
return nil , "" , err
}
defer rows . Close ( )
var (
result [ ] * common . Message
cursors [ ] string
)
for rows . Next ( ) {
var (
message common . Message
cursor string
)
if err := db . tableUserMessagesScanAllFields ( rows , & message , & cursor ) ; err != nil {
return nil , "" , err
}
result = append ( result , & message )
cursors = append ( cursors , cursor )
}
var newCursor string
if len ( result ) > limit {
newCursor = cursors [ limit ]
result = result [ : limit ]
}
return result , newCursor , nil
}
2020-07-27 15:57:01 +00:00
// EmojiReactionsByChatID returns the emoji reactions for the queried messages, up to a maximum of 100, as it's a potentially unbound number.
// NOTE: This is not completely accurate, as the messages in the database might have change since the last call to `MessageByChatID`.
func ( db sqlitePersistence ) EmojiReactionsByChatID ( chatID string , currCursor string , limit int ) ( [ ] * EmojiReaction , error ) {
cursorWhere := ""
if currCursor != "" {
2020-11-16 11:54:39 +00:00
cursorWhere = "AND substr('0000000000000000000000000000000000000000000000000000000000000000' || m.clock_value, -64, 64) || m.id <= ?" //nolint: goconst
2020-07-27 15:57:01 +00:00
}
2020-07-28 07:53:32 +00:00
args := [ ] interface { } { chatID , chatID }
2020-07-27 15:57:01 +00:00
if currCursor != "" {
args = append ( args , currCursor )
}
2020-07-28 05:41:50 +00:00
args = append ( args , limit )
2020-07-28 07:53:32 +00:00
// NOTE: We match against local_chat_id for security reasons.
// As a user could potentially send an emoji reaction for a one to
// one/group chat that has no access to.
2020-07-29 12:00:51 +00:00
// We also limit the number of emoji to a reasonable number (1000)
// for now, as we don't want the client to choke on this.
// The issue is that your own emoji might not be returned in such cases,
// allowing the user to react to a post multiple times.
// Jakubgs: Returning the whole list seems like a real overkill.
// This will get very heavy in threads that have loads of reactions on loads of messages.
// A more sensible response would just include a count and a bool telling you if you are in the list.
2020-07-28 08:02:51 +00:00
// nolint: gosec
2020-07-28 05:41:50 +00:00
query := fmt . Sprintf ( `
2020-07-27 15:57:01 +00:00
SELECT
e . clock_value ,
e . source ,
e . emoji_id ,
e . message_id ,
e . chat_id ,
2020-07-28 07:53:32 +00:00
e . local_chat_id ,
2020-07-27 15:57:01 +00:00
e . retracted
FROM
emoji_reactions e
WHERE NOT ( e . retracted )
AND
2020-07-28 07:53:32 +00:00
e . local_chat_id = ?
AND
2020-07-27 15:57:01 +00:00
e . message_id IN
( SELECT id FROM user_messages m WHERE NOT ( m . hide ) AND m . local_chat_id = ? % s
ORDER BY substr ( ' 0000000000000000000000000000000000000000000000000000000000000000 ' || m . clock_value , - 64 , 64 ) || m . id DESC LIMIT ? )
2020-07-29 12:00:51 +00:00
LIMIT 1000
2020-07-28 05:41:50 +00:00
` , cursorWhere )
rows , err := db . db . Query (
query ,
args ... ,
2020-07-27 15:57:01 +00:00
)
if err != nil {
return nil , err
}
defer rows . Close ( )
2020-11-16 11:54:39 +00:00
var result [ ] * EmojiReaction
for rows . Next ( ) {
var emojiReaction EmojiReaction
err := rows . Scan ( & emojiReaction . Clock ,
& emojiReaction . From ,
& emojiReaction . Type ,
& emojiReaction . MessageId ,
& emojiReaction . ChatId ,
& emojiReaction . LocalChatID ,
& emojiReaction . Retracted )
if err != nil {
return nil , err
}
result = append ( result , & emojiReaction )
}
return result , nil
}
// EmojiReactionsByChatIDs returns the emoji reactions for the queried messages, up to a maximum of 100, as it's a potentially unbound number.
// NOTE: This is not completely accurate, as the messages in the database might have change since the last call to `MessageByChatID`.
func ( db sqlitePersistence ) EmojiReactionsByChatIDs ( chatIDs [ ] string , currCursor string , limit int ) ( [ ] * EmojiReaction , error ) {
cursorWhere := ""
if currCursor != "" {
cursorWhere = "AND substr('0000000000000000000000000000000000000000000000000000000000000000' || m.clock_value, -64, 64) || m.id <= ?" //nolint: goconst
}
chatsLen := len ( chatIDs )
args := make ( [ ] interface { } , chatsLen * 2 )
for i , v := range chatIDs {
args [ i ] = v
}
for i , v := range chatIDs {
args [ chatsLen + i ] = v
}
if currCursor != "" {
args = append ( args , currCursor )
}
args = append ( args , limit )
// NOTE: We match against local_chat_id for security reasons.
// As a user could potentially send an emoji reaction for a one to
// one/group chat that has no access to.
// We also limit the number of emoji to a reasonable number (1000)
// for now, as we don't want the client to choke on this.
// The issue is that your own emoji might not be returned in such cases,
// allowing the user to react to a post multiple times.
// Jakubgs: Returning the whole list seems like a real overkill.
// This will get very heavy in threads that have loads of reactions on loads of messages.
// A more sensible response would just include a count and a bool telling you if you are in the list.
// nolint: gosec
query := fmt . Sprintf ( `
SELECT
e . clock_value ,
e . source ,
e . emoji_id ,
e . message_id ,
e . chat_id ,
e . local_chat_id ,
e . retracted
FROM
emoji_reactions e
WHERE NOT ( e . retracted )
AND
e . local_chat_id IN % s
AND
e . message_id IN
( SELECT id FROM user_messages m WHERE NOT ( m . hide ) AND m . local_chat_id IN % s % s
ORDER BY substr ( ' 0000000000000000000000000000000000000000000000000000000000000000 ' || m . clock_value , - 64 , 64 ) || m . id DESC LIMIT ? )
LIMIT 1000
` , "(?" + strings . Repeat ( ",?" , chatsLen - 1 ) + ")" , "(?" + strings . Repeat ( ",?" , chatsLen - 1 ) + ")" , cursorWhere )
rows , err := db . db . Query (
query ,
args ... ,
)
if err != nil {
return nil , err
}
defer rows . Close ( )
2020-07-27 15:57:01 +00:00
var result [ ] * EmojiReaction
for rows . Next ( ) {
var emojiReaction EmojiReaction
err := rows . Scan ( & emojiReaction . Clock ,
& emojiReaction . From ,
& emojiReaction . Type ,
& emojiReaction . MessageId ,
& emojiReaction . ChatId ,
2020-07-28 07:53:32 +00:00
& emojiReaction . LocalChatID ,
2020-07-27 15:57:01 +00:00
& emojiReaction . Retracted )
if err != nil {
return nil , err
}
result = append ( result , & emojiReaction )
}
return result , nil
}
2020-09-01 13:27:01 +00:00
func ( db sqlitePersistence ) SaveMessages ( messages [ ] * common . Message ) ( err error ) {
2019-11-15 08:52:28 +00:00
tx , err := db . db . BeginTx ( context . Background ( ) , & sql . TxOptions { } )
2019-08-06 21:50:13 +00:00
if err != nil {
2019-11-15 08:52:28 +00:00
return
2019-08-06 21:50:13 +00:00
}
2019-08-20 11:20:25 +00:00
defer func ( ) {
if err == nil {
err = tx . Commit ( )
return
2019-08-06 21:50:13 +00:00
}
2019-08-20 11:20:25 +00:00
// don't shadow original error
_ = tx . Rollback ( )
} ( )
2019-08-06 21:50:13 +00:00
2020-05-20 12:16:12 +00:00
allFields := db . tableUserMessagesAllFields ( )
valuesVector := strings . Repeat ( "?, " , db . tableUserMessagesAllFieldsCount ( ) - 1 ) + "?"
2020-02-10 11:22:37 +00:00
query := "INSERT INTO user_messages(" + allFields + ") VALUES (" + valuesVector + ")" // nolint: gosec
2019-11-15 08:52:28 +00:00
stmt , err := tx . Prepare ( query )
2019-08-06 21:50:13 +00:00
if err != nil {
2019-11-15 08:52:28 +00:00
return
2019-08-06 21:50:13 +00:00
}
2019-08-20 11:20:25 +00:00
for _ , msg := range messages {
Move to protobuf for Message type (#1706)
* Use a single Message type `v1/message.go` and `message.go` are the same now, and they embed `protobuf.ChatMessage`
* Use `SendChatMessage` for sending chat messages, this is basically the old `Send` but a bit more flexible so we can send different message types (stickers,commands), and not just text.
* Remove dedup from services/shhext. Because now we process in status-protocol, dedup makes less sense, as those messages are going to be processed anyway, so removing for now, we can re-evaluate if bringing it to status-go or not.
* Change the various retrieveX method to a single one:
`RetrieveAll` will be processing those messages that it can process (Currently only `Message`), and return the rest in `RawMessages` (still transit). The format for the response is:
`Chats`: -> The chats updated by receiving the message
`Messages`: -> The messages retrieved (already matched to a chat)
`Contacts`: -> The contacts updated by the messages
`RawMessages` -> Anything else that can't be parsed, eventually as we move everything to status-protocol-go this will go away.
2019-12-05 16:25:34 +00:00
var allValues [ ] interface { }
2020-05-20 12:16:12 +00:00
allValues , err = db . tableUserMessagesAllValues ( msg )
Move to protobuf for Message type (#1706)
* Use a single Message type `v1/message.go` and `message.go` are the same now, and they embed `protobuf.ChatMessage`
* Use `SendChatMessage` for sending chat messages, this is basically the old `Send` but a bit more flexible so we can send different message types (stickers,commands), and not just text.
* Remove dedup from services/shhext. Because now we process in status-protocol, dedup makes less sense, as those messages are going to be processed anyway, so removing for now, we can re-evaluate if bringing it to status-go or not.
* Change the various retrieveX method to a single one:
`RetrieveAll` will be processing those messages that it can process (Currently only `Message`), and return the rest in `RawMessages` (still transit). The format for the response is:
`Chats`: -> The chats updated by receiving the message
`Messages`: -> The messages retrieved (already matched to a chat)
`Contacts`: -> The contacts updated by the messages
`RawMessages` -> Anything else that can't be parsed, eventually as we move everything to status-protocol-go this will go away.
2019-12-05 16:25:34 +00:00
if err != nil {
return
}
_ , err = stmt . Exec ( allValues ... )
2019-08-20 11:20:25 +00:00
if err != nil {
2019-11-15 08:52:28 +00:00
return
2019-08-06 21:50:13 +00:00
}
}
2019-11-15 08:52:28 +00:00
return
2019-08-06 21:50:13 +00:00
}
2021-05-14 21:22:50 +00:00
func ( db sqlitePersistence ) SavePinMessages ( messages [ ] * common . PinMessage ) ( err error ) {
tx , err := db . db . BeginTx ( context . Background ( ) , nil )
if err != nil {
return
}
defer func ( ) {
if err == nil {
err = tx . Commit ( )
return
}
// don't shadow original error
_ = tx . Rollback ( )
} ( )
// select
selectQuery := "SELECT clock_value FROM pin_messages WHERE id = ?"
// insert
2021-06-08 15:23:32 +00:00
allInsertFields := ` id, message_id, whisper_timestamp, chat_id, local_chat_id, clock_value, pinned, pinned_by `
2021-05-14 21:22:50 +00:00
insertValues := strings . Repeat ( "?, " , strings . Count ( allInsertFields , "," ) ) + "?"
insertQuery := "INSERT INTO pin_messages(" + allInsertFields + ") VALUES (" + insertValues + ")" // nolint: gosec
insertStmt , err := tx . Prepare ( insertQuery )
if err != nil {
return
}
// update
2021-06-08 15:23:32 +00:00
updateQuery := "UPDATE pin_messages SET pinned = ?, clock_value = ?, pinned_by = ? WHERE id = ?"
2021-05-14 21:22:50 +00:00
updateStmt , err := tx . Prepare ( updateQuery )
if err != nil {
return
}
for _ , message := range messages {
row := tx . QueryRow ( selectQuery , message . ID )
var existingClock uint64
switch err = row . Scan ( & existingClock ) ; err {
case sql . ErrNoRows :
// not found, insert new record
allValues := [ ] interface { } {
message . ID ,
message . MessageId ,
message . WhisperTimestamp ,
message . ChatId ,
message . LocalChatID ,
message . Clock ,
message . Pinned ,
2021-06-08 15:23:32 +00:00
message . From ,
2021-05-14 21:22:50 +00:00
}
_ , err = insertStmt . Exec ( allValues ... )
if err != nil {
return
}
case nil :
// found, update if current message is more recent, otherwise skip
if existingClock < message . Clock {
// update
2021-06-08 15:23:32 +00:00
_ , err = updateStmt . Exec ( message . Pinned , message . Clock , message . From , message . ID )
2021-05-14 21:22:50 +00:00
if err != nil {
return
}
}
default :
return
}
}
return
}
2019-08-06 21:50:13 +00:00
func ( db sqlitePersistence ) DeleteMessage ( id string ) error {
2020-01-10 18:59:01 +00:00
_ , err := db . db . Exec ( ` DELETE FROM user_messages WHERE id = ? ` , id )
return err
}
2021-03-25 15:15:22 +00:00
func ( db sqlitePersistence ) DeleteMessages ( ids [ ] string ) error {
idsArgs := make ( [ ] interface { } , 0 , len ( ids ) )
for _ , id := range ids {
idsArgs = append ( idsArgs , id )
}
inVector := strings . Repeat ( "?, " , len ( ids ) - 1 ) + "?"
_ , err := db . db . Exec ( "DELETE FROM user_messages WHERE id IN (" + inVector + ")" , idsArgs ... ) // nolint: gosec
return err
}
2020-01-10 18:59:01 +00:00
func ( db sqlitePersistence ) HideMessage ( id string ) error {
2020-12-07 15:13:39 +00:00
_ , err := db . db . Exec ( ` UPDATE user_messages SET hide = 1, seen = 1 WHERE id = ? ` , id )
2019-08-06 21:50:13 +00:00
return err
}
2019-08-20 11:20:25 +00:00
func ( db sqlitePersistence ) DeleteMessagesByChatID ( id string ) error {
2020-12-22 10:49:25 +00:00
return db . deleteMessagesByChatID ( id , nil )
}
func ( db sqlitePersistence ) deleteMessagesByChatID ( id string , tx * sql . Tx ) ( err error ) {
if tx == nil {
tx , err = db . db . BeginTx ( context . Background ( ) , & sql . TxOptions { } )
if err != nil {
return err
}
defer func ( ) {
if err == nil {
err = tx . Commit ( )
return
}
// don't shadow original error
_ = tx . Rollback ( )
} ( )
}
_ , err = tx . Exec ( ` DELETE FROM user_messages WHERE local_chat_id = ? ` , id )
2021-05-14 21:22:50 +00:00
if err != nil {
return
}
_ , err = tx . Exec ( ` DELETE FROM pin_messages WHERE local_chat_id = ? ` , id )
2020-12-22 10:49:25 +00:00
return
2019-08-20 11:20:25 +00:00
}
2020-02-26 12:31:48 +00:00
func ( db sqlitePersistence ) MarkAllRead ( chatID string ) error {
tx , err := db . db . BeginTx ( context . Background ( ) , & sql . TxOptions { } )
if err != nil {
return err
}
defer func ( ) {
if err == nil {
err = tx . Commit ( )
return
}
// don't shadow original error
_ = tx . Rollback ( )
} ( )
2020-09-10 06:57:45 +00:00
_ , err = tx . Exec ( ` UPDATE user_messages SET seen = 1 WHERE local_chat_id = ? AND seen != 1 ` , chatID )
2020-02-26 12:31:48 +00:00
if err != nil {
return err
}
2021-05-26 06:38:25 +00:00
_ , err = tx . Exec ( ` UPDATE chats SET unviewed_mentions_count = 0, unviewed_message_count = 0 WHERE id = ? ` , chatID )
2020-02-26 12:31:48 +00:00
return err
}
2020-04-06 12:08:53 +00:00
func ( db sqlitePersistence ) MarkMessagesSeen ( chatID string , ids [ ] string ) ( uint64 , error ) {
Move to protobuf for Message type (#1706)
* Use a single Message type `v1/message.go` and `message.go` are the same now, and they embed `protobuf.ChatMessage`
* Use `SendChatMessage` for sending chat messages, this is basically the old `Send` but a bit more flexible so we can send different message types (stickers,commands), and not just text.
* Remove dedup from services/shhext. Because now we process in status-protocol, dedup makes less sense, as those messages are going to be processed anyway, so removing for now, we can re-evaluate if bringing it to status-go or not.
* Change the various retrieveX method to a single one:
`RetrieveAll` will be processing those messages that it can process (Currently only `Message`), and return the rest in `RawMessages` (still transit). The format for the response is:
`Chats`: -> The chats updated by receiving the message
`Messages`: -> The messages retrieved (already matched to a chat)
`Contacts`: -> The contacts updated by the messages
`RawMessages` -> Anything else that can't be parsed, eventually as we move everything to status-protocol-go this will go away.
2019-12-05 16:25:34 +00:00
tx , err := db . db . BeginTx ( context . Background ( ) , & sql . TxOptions { } )
if err != nil {
2020-04-06 12:08:53 +00:00
return 0 , err
Move to protobuf for Message type (#1706)
* Use a single Message type `v1/message.go` and `message.go` are the same now, and they embed `protobuf.ChatMessage`
* Use `SendChatMessage` for sending chat messages, this is basically the old `Send` but a bit more flexible so we can send different message types (stickers,commands), and not just text.
* Remove dedup from services/shhext. Because now we process in status-protocol, dedup makes less sense, as those messages are going to be processed anyway, so removing for now, we can re-evaluate if bringing it to status-go or not.
* Change the various retrieveX method to a single one:
`RetrieveAll` will be processing those messages that it can process (Currently only `Message`), and return the rest in `RawMessages` (still transit). The format for the response is:
`Chats`: -> The chats updated by receiving the message
`Messages`: -> The messages retrieved (already matched to a chat)
`Contacts`: -> The contacts updated by the messages
`RawMessages` -> Anything else that can't be parsed, eventually as we move everything to status-protocol-go this will go away.
2019-12-05 16:25:34 +00:00
}
defer func ( ) {
if err == nil {
err = tx . Commit ( )
return
}
// don't shadow original error
_ = tx . Rollback ( )
} ( )
2019-08-06 21:50:13 +00:00
idsArgs := make ( [ ] interface { } , 0 , len ( ids ) )
for _ , id := range ids {
idsArgs = append ( idsArgs , id )
}
inVector := strings . Repeat ( "?, " , len ( ids ) - 1 ) + "?"
2020-12-07 15:13:39 +00:00
q := "UPDATE user_messages SET seen = 1 WHERE NOT(seen) AND id IN (" + inVector + ")" // nolint: gosec
2020-02-10 11:22:37 +00:00
_ , err = tx . Exec ( q , idsArgs ... )
Move to protobuf for Message type (#1706)
* Use a single Message type `v1/message.go` and `message.go` are the same now, and they embed `protobuf.ChatMessage`
* Use `SendChatMessage` for sending chat messages, this is basically the old `Send` but a bit more flexible so we can send different message types (stickers,commands), and not just text.
* Remove dedup from services/shhext. Because now we process in status-protocol, dedup makes less sense, as those messages are going to be processed anyway, so removing for now, we can re-evaluate if bringing it to status-go or not.
* Change the various retrieveX method to a single one:
`RetrieveAll` will be processing those messages that it can process (Currently only `Message`), and return the rest in `RawMessages` (still transit). The format for the response is:
`Chats`: -> The chats updated by receiving the message
`Messages`: -> The messages retrieved (already matched to a chat)
`Contacts`: -> The contacts updated by the messages
`RawMessages` -> Anything else that can't be parsed, eventually as we move everything to status-protocol-go this will go away.
2019-12-05 16:25:34 +00:00
if err != nil {
2020-04-06 12:08:53 +00:00
return 0 , err
}
var count uint64
row := tx . QueryRow ( "SELECT changes();" )
if err := row . Scan ( & count ) ; err != nil {
return 0 , err
Move to protobuf for Message type (#1706)
* Use a single Message type `v1/message.go` and `message.go` are the same now, and they embed `protobuf.ChatMessage`
* Use `SendChatMessage` for sending chat messages, this is basically the old `Send` but a bit more flexible so we can send different message types (stickers,commands), and not just text.
* Remove dedup from services/shhext. Because now we process in status-protocol, dedup makes less sense, as those messages are going to be processed anyway, so removing for now, we can re-evaluate if bringing it to status-go or not.
* Change the various retrieveX method to a single one:
`RetrieveAll` will be processing those messages that it can process (Currently only `Message`), and return the rest in `RawMessages` (still transit). The format for the response is:
`Chats`: -> The chats updated by receiving the message
`Messages`: -> The messages retrieved (already matched to a chat)
`Contacts`: -> The contacts updated by the messages
`RawMessages` -> Anything else that can't be parsed, eventually as we move everything to status-protocol-go this will go away.
2019-12-05 16:25:34 +00:00
}
// Update denormalized count
_ , err = tx . Exec (
` UPDATE chats
SET unviewed_message_count =
( SELECT COUNT ( 1 )
2020-01-10 18:59:01 +00:00
FROM user_messages
2021-05-26 06:38:25 +00:00
WHERE local_chat_id = ? AND seen = 0 ) ,
unviewed_mentions_count =
( SELECT COUNT ( 1 )
FROM user_messages
WHERE local_chat_id = ? AND seen = 0 AND mentioned )
WHERE id = ? ` , chatID , chatID , chatID )
2020-04-06 12:08:53 +00:00
return count , err
2019-08-06 21:50:13 +00:00
}
func ( db sqlitePersistence ) UpdateMessageOutgoingStatus ( id string , newOutgoingStatus string ) error {
_ , err := db . db . Exec ( `
2020-01-10 18:59:01 +00:00
UPDATE user_messages
2019-08-06 21:50:13 +00:00
SET outgoing_status = ?
WHERE id = ?
` , newOutgoingStatus , id )
return err
}
2019-08-20 11:20:25 +00:00
// BlockContact updates a contact, deletes all the messages and 1-to-1 chat, updates the unread messages count and returns a map with the new count
2019-12-02 15:34:05 +00:00
func ( db sqlitePersistence ) BlockContact ( contact * Contact ) ( [ ] * Chat , error ) {
Move to protobuf for Message type (#1706)
* Use a single Message type `v1/message.go` and `message.go` are the same now, and they embed `protobuf.ChatMessage`
* Use `SendChatMessage` for sending chat messages, this is basically the old `Send` but a bit more flexible so we can send different message types (stickers,commands), and not just text.
* Remove dedup from services/shhext. Because now we process in status-protocol, dedup makes less sense, as those messages are going to be processed anyway, so removing for now, we can re-evaluate if bringing it to status-go or not.
* Change the various retrieveX method to a single one:
`RetrieveAll` will be processing those messages that it can process (Currently only `Message`), and return the rest in `RawMessages` (still transit). The format for the response is:
`Chats`: -> The chats updated by receiving the message
`Messages`: -> The messages retrieved (already matched to a chat)
`Contacts`: -> The contacts updated by the messages
`RawMessages` -> Anything else that can't be parsed, eventually as we move everything to status-protocol-go this will go away.
2019-12-05 16:25:34 +00:00
var chats [ ] * Chat
2019-11-15 08:52:28 +00:00
tx , err := db . db . BeginTx ( context . Background ( ) , & sql . TxOptions { } )
2019-08-20 11:20:25 +00:00
if err != nil {
Move to protobuf for Message type (#1706)
* Use a single Message type `v1/message.go` and `message.go` are the same now, and they embed `protobuf.ChatMessage`
* Use `SendChatMessage` for sending chat messages, this is basically the old `Send` but a bit more flexible so we can send different message types (stickers,commands), and not just text.
* Remove dedup from services/shhext. Because now we process in status-protocol, dedup makes less sense, as those messages are going to be processed anyway, so removing for now, we can re-evaluate if bringing it to status-go or not.
* Change the various retrieveX method to a single one:
`RetrieveAll` will be processing those messages that it can process (Currently only `Message`), and return the rest in `RawMessages` (still transit). The format for the response is:
`Chats`: -> The chats updated by receiving the message
`Messages`: -> The messages retrieved (already matched to a chat)
`Contacts`: -> The contacts updated by the messages
`RawMessages` -> Anything else that can't be parsed, eventually as we move everything to status-protocol-go this will go away.
2019-12-05 16:25:34 +00:00
return nil , err
2019-08-20 11:20:25 +00:00
}
defer func ( ) {
if err == nil {
err = tx . Commit ( )
return
}
// don't shadow original error
_ = tx . Rollback ( )
} ( )
// Delete messages
_ , err = tx . Exec (
` DELETE
2020-01-10 18:59:01 +00:00
FROM user_messages
2019-08-20 11:20:25 +00:00
WHERE source = ? ` ,
contact . ID ,
)
if err != nil {
Move to protobuf for Message type (#1706)
* Use a single Message type `v1/message.go` and `message.go` are the same now, and they embed `protobuf.ChatMessage`
* Use `SendChatMessage` for sending chat messages, this is basically the old `Send` but a bit more flexible so we can send different message types (stickers,commands), and not just text.
* Remove dedup from services/shhext. Because now we process in status-protocol, dedup makes less sense, as those messages are going to be processed anyway, so removing for now, we can re-evaluate if bringing it to status-go or not.
* Change the various retrieveX method to a single one:
`RetrieveAll` will be processing those messages that it can process (Currently only `Message`), and return the rest in `RawMessages` (still transit). The format for the response is:
`Chats`: -> The chats updated by receiving the message
`Messages`: -> The messages retrieved (already matched to a chat)
`Contacts`: -> The contacts updated by the messages
`RawMessages` -> Anything else that can't be parsed, eventually as we move everything to status-protocol-go this will go away.
2019-12-05 16:25:34 +00:00
return nil , err
2019-08-20 11:20:25 +00:00
}
// Update contact
err = db . SaveContact ( contact , tx )
if err != nil {
Move to protobuf for Message type (#1706)
* Use a single Message type `v1/message.go` and `message.go` are the same now, and they embed `protobuf.ChatMessage`
* Use `SendChatMessage` for sending chat messages, this is basically the old `Send` but a bit more flexible so we can send different message types (stickers,commands), and not just text.
* Remove dedup from services/shhext. Because now we process in status-protocol, dedup makes less sense, as those messages are going to be processed anyway, so removing for now, we can re-evaluate if bringing it to status-go or not.
* Change the various retrieveX method to a single one:
`RetrieveAll` will be processing those messages that it can process (Currently only `Message`), and return the rest in `RawMessages` (still transit). The format for the response is:
`Chats`: -> The chats updated by receiving the message
`Messages`: -> The messages retrieved (already matched to a chat)
`Contacts`: -> The contacts updated by the messages
`RawMessages` -> Anything else that can't be parsed, eventually as we move everything to status-protocol-go this will go away.
2019-12-05 16:25:34 +00:00
return nil , err
2019-08-20 11:20:25 +00:00
}
// Delete one-to-one chat
_ , err = tx . Exec ( "DELETE FROM chats WHERE id = ?" , contact . ID )
if err != nil {
Move to protobuf for Message type (#1706)
* Use a single Message type `v1/message.go` and `message.go` are the same now, and they embed `protobuf.ChatMessage`
* Use `SendChatMessage` for sending chat messages, this is basically the old `Send` but a bit more flexible so we can send different message types (stickers,commands), and not just text.
* Remove dedup from services/shhext. Because now we process in status-protocol, dedup makes less sense, as those messages are going to be processed anyway, so removing for now, we can re-evaluate if bringing it to status-go or not.
* Change the various retrieveX method to a single one:
`RetrieveAll` will be processing those messages that it can process (Currently only `Message`), and return the rest in `RawMessages` (still transit). The format for the response is:
`Chats`: -> The chats updated by receiving the message
`Messages`: -> The messages retrieved (already matched to a chat)
`Contacts`: -> The contacts updated by the messages
`RawMessages` -> Anything else that can't be parsed, eventually as we move everything to status-protocol-go this will go away.
2019-12-05 16:25:34 +00:00
return nil , err
2019-08-20 11:20:25 +00:00
}
// Recalculate denormalized fields
_ , err = tx . Exec ( `
2019-11-15 08:52:28 +00:00
UPDATE chats
SET
2021-05-26 06:38:25 +00:00
unviewed_message_count = ( SELECT COUNT ( 1 ) FROM user_messages WHERE seen = 0 AND local_chat_id = chats . id ) ,
unviewed_mentions_count = ( SELECT COUNT ( 1 ) FROM user_messages WHERE seen = 0 AND local_chat_id = chats . id AND mentioned ) ` )
2019-08-20 11:20:25 +00:00
if err != nil {
Move to protobuf for Message type (#1706)
* Use a single Message type `v1/message.go` and `message.go` are the same now, and they embed `protobuf.ChatMessage`
* Use `SendChatMessage` for sending chat messages, this is basically the old `Send` but a bit more flexible so we can send different message types (stickers,commands), and not just text.
* Remove dedup from services/shhext. Because now we process in status-protocol, dedup makes less sense, as those messages are going to be processed anyway, so removing for now, we can re-evaluate if bringing it to status-go or not.
* Change the various retrieveX method to a single one:
`RetrieveAll` will be processing those messages that it can process (Currently only `Message`), and return the rest in `RawMessages` (still transit). The format for the response is:
`Chats`: -> The chats updated by receiving the message
`Messages`: -> The messages retrieved (already matched to a chat)
`Contacts`: -> The contacts updated by the messages
`RawMessages` -> Anything else that can't be parsed, eventually as we move everything to status-protocol-go this will go away.
2019-12-05 16:25:34 +00:00
return nil , err
2019-08-20 11:20:25 +00:00
}
// return the updated chats
2019-11-15 08:52:28 +00:00
chats , err = db . chats ( tx )
Move to protobuf for Message type (#1706)
* Use a single Message type `v1/message.go` and `message.go` are the same now, and they embed `protobuf.ChatMessage`
* Use `SendChatMessage` for sending chat messages, this is basically the old `Send` but a bit more flexible so we can send different message types (stickers,commands), and not just text.
* Remove dedup from services/shhext. Because now we process in status-protocol, dedup makes less sense, as those messages are going to be processed anyway, so removing for now, we can re-evaluate if bringing it to status-go or not.
* Change the various retrieveX method to a single one:
`RetrieveAll` will be processing those messages that it can process (Currently only `Message`), and return the rest in `RawMessages` (still transit). The format for the response is:
`Chats`: -> The chats updated by receiving the message
`Messages`: -> The messages retrieved (already matched to a chat)
`Contacts`: -> The contacts updated by the messages
`RawMessages` -> Anything else that can't be parsed, eventually as we move everything to status-protocol-go this will go away.
2019-12-05 16:25:34 +00:00
if err != nil {
return nil , err
}
for _ , c := range chats {
var lastMessageID string
2020-01-10 18:59:01 +00:00
row := tx . QueryRow ( ` SELECT id FROM user_messages WHERE local_chat_id = ? ORDER BY clock_value DESC LIMIT 1 ` , c . ID )
Move to protobuf for Message type (#1706)
* Use a single Message type `v1/message.go` and `message.go` are the same now, and they embed `protobuf.ChatMessage`
* Use `SendChatMessage` for sending chat messages, this is basically the old `Send` but a bit more flexible so we can send different message types (stickers,commands), and not just text.
* Remove dedup from services/shhext. Because now we process in status-protocol, dedup makes less sense, as those messages are going to be processed anyway, so removing for now, we can re-evaluate if bringing it to status-go or not.
* Change the various retrieveX method to a single one:
`RetrieveAll` will be processing those messages that it can process (Currently only `Message`), and return the rest in `RawMessages` (still transit). The format for the response is:
`Chats`: -> The chats updated by receiving the message
`Messages`: -> The messages retrieved (already matched to a chat)
`Contacts`: -> The contacts updated by the messages
`RawMessages` -> Anything else that can't be parsed, eventually as we move everything to status-protocol-go this will go away.
2019-12-05 16:25:34 +00:00
switch err := row . Scan ( & lastMessageID ) ; err {
case nil :
message , err := db . messageByID ( tx , lastMessageID )
if err != nil {
return nil , err
}
if message != nil {
encodedMessage , err := json . Marshal ( message )
if err != nil {
return nil , err
}
_ , err = tx . Exec ( ` UPDATE chats SET last_message = ? WHERE id = ? ` , encodedMessage , c . ID )
if err != nil {
return nil , err
}
2020-07-30 20:54:33 +00:00
c . LastMessage = message
Move to protobuf for Message type (#1706)
* Use a single Message type `v1/message.go` and `message.go` are the same now, and they embed `protobuf.ChatMessage`
* Use `SendChatMessage` for sending chat messages, this is basically the old `Send` but a bit more flexible so we can send different message types (stickers,commands), and not just text.
* Remove dedup from services/shhext. Because now we process in status-protocol, dedup makes less sense, as those messages are going to be processed anyway, so removing for now, we can re-evaluate if bringing it to status-go or not.
* Change the various retrieveX method to a single one:
`RetrieveAll` will be processing those messages that it can process (Currently only `Message`), and return the rest in `RawMessages` (still transit). The format for the response is:
`Chats`: -> The chats updated by receiving the message
`Messages`: -> The messages retrieved (already matched to a chat)
`Contacts`: -> The contacts updated by the messages
`RawMessages` -> Anything else that can't be parsed, eventually as we move everything to status-protocol-go this will go away.
2019-12-05 16:25:34 +00:00
}
case sql . ErrNoRows :
// Reset LastMessage
_ , err = tx . Exec ( ` UPDATE chats SET last_message = NULL WHERE id = ? ` , c . ID )
if err != nil {
return nil , err
}
c . LastMessage = nil
default :
return nil , err
}
}
return chats , err
2019-08-20 11:20:25 +00:00
}
2020-07-21 23:42:55 +00:00
func ( db sqlitePersistence ) SaveEmojiReaction ( emojiReaction * EmojiReaction ) ( err error ) {
2020-07-28 07:53:32 +00:00
query := "INSERT INTO emoji_reactions(id,clock_value,source,emoji_id,message_id,chat_id,local_chat_id,retracted) VALUES (?,?,?,?,?,?,?,?)"
2020-07-27 12:27:48 +00:00
stmt , err := db . db . Prepare ( query )
2020-07-21 23:42:55 +00:00
if err != nil {
return
}
2020-07-27 12:27:48 +00:00
_ , err = stmt . Exec (
emojiReaction . ID ( ) ,
2020-07-21 23:42:55 +00:00
emojiReaction . Clock ,
emojiReaction . From ,
2020-07-25 16:13:08 +00:00
emojiReaction . Type ,
emojiReaction . MessageId ,
emojiReaction . ChatId ,
2020-07-28 07:53:32 +00:00
emojiReaction . LocalChatID ,
2020-07-21 23:42:55 +00:00
emojiReaction . Retracted ,
2020-07-27 12:27:48 +00:00
)
2020-07-21 23:42:55 +00:00
return
}
2020-07-22 00:21:05 +00:00
func ( db sqlitePersistence ) EmojiReactionByID ( id string ) ( * EmojiReaction , error ) {
2020-07-28 07:53:32 +00:00
row := db . db . QueryRow (
2020-07-27 12:27:48 +00:00
` SELECT
clock_value ,
source ,
emoji_id ,
message_id ,
chat_id ,
2020-07-28 07:53:32 +00:00
local_chat_id ,
2020-07-27 12:27:48 +00:00
retracted
2020-07-22 00:21:05 +00:00
FROM
emoji_reactions
WHERE
emoji_reactions . id = ?
2020-07-27 12:27:48 +00:00
` , id )
2020-07-22 00:21:05 +00:00
emojiReaction := new ( EmojiReaction )
2020-07-28 07:53:32 +00:00
err := row . Scan ( & emojiReaction . Clock ,
2020-07-22 00:21:05 +00:00
& emojiReaction . From ,
2020-07-25 16:13:08 +00:00
& emojiReaction . Type ,
& emojiReaction . MessageId ,
& emojiReaction . ChatId ,
2020-07-28 07:53:32 +00:00
& emojiReaction . LocalChatID ,
2020-07-22 00:21:05 +00:00
& emojiReaction . Retracted ,
2020-07-27 12:27:48 +00:00
)
switch err {
case sql . ErrNoRows :
2020-10-08 10:46:03 +00:00
return nil , common . ErrRecordNotFound
2020-07-27 12:27:48 +00:00
case nil :
return emojiReaction , nil
default :
return nil , err
}
}
2020-08-07 13:49:37 +00:00
func ( db sqlitePersistence ) SaveInvitation ( invitation * GroupChatInvitation ) ( err error ) {
query := "INSERT INTO group_chat_invitations(id,source,chat_id,message,state,clock) VALUES (?,?,?,?,?,?)"
stmt , err := db . db . Prepare ( query )
if err != nil {
return
}
_ , err = stmt . Exec (
invitation . ID ( ) ,
invitation . From ,
invitation . ChatId ,
invitation . IntroductionMessage ,
invitation . State ,
invitation . Clock ,
)
return
}
func ( db sqlitePersistence ) GetGroupChatInvitations ( ) ( rst [ ] * GroupChatInvitation , err error ) {
tx , err := db . db . Begin ( )
if err != nil {
return
}
defer func ( ) {
if err == nil {
err = tx . Commit ( )
return
}
_ = tx . Rollback ( )
} ( )
bRows , err := tx . Query ( ` SELECT
source ,
chat_id ,
message ,
state ,
clock
FROM
group_chat_invitations ` )
if err != nil {
return
}
defer bRows . Close ( )
for bRows . Next ( ) {
invitation := GroupChatInvitation { }
err = bRows . Scan (
& invitation . From ,
& invitation . ChatId ,
& invitation . IntroductionMessage ,
& invitation . State ,
& invitation . Clock )
if err != nil {
return nil , err
}
rst = append ( rst , & invitation )
}
return rst , nil
}
func ( db sqlitePersistence ) InvitationByID ( id string ) ( * GroupChatInvitation , error ) {
row := db . db . QueryRow (
` SELECT
source ,
chat_id ,
message ,
state ,
clock
FROM
group_chat_invitations
WHERE
group_chat_invitations . id = ?
` , id )
chatInvitations := new ( GroupChatInvitation )
err := row . Scan ( & chatInvitations . From ,
& chatInvitations . ChatId ,
& chatInvitations . IntroductionMessage ,
& chatInvitations . State ,
& chatInvitations . Clock ,
)
switch err {
case sql . ErrNoRows :
2020-10-08 10:46:03 +00:00
return nil , common . ErrRecordNotFound
2020-08-07 13:49:37 +00:00
case nil :
return chatInvitations , nil
default :
return nil , err
}
}
2020-12-22 10:49:25 +00:00
// ClearHistory deletes all the messages for a chat and updates it's values
func ( db sqlitePersistence ) ClearHistory ( chat * Chat , currentClockValue uint64 ) ( err error ) {
var tx * sql . Tx
tx , err = db . db . BeginTx ( context . Background ( ) , & sql . TxOptions { } )
if err != nil {
return
}
defer func ( ) {
if err == nil {
err = tx . Commit ( )
return
}
// don't shadow original error
_ = tx . Rollback ( )
} ( )
2021-05-14 10:55:42 +00:00
err = db . clearHistory ( chat , currentClockValue , tx , false )
2020-12-22 10:49:25 +00:00
return
}
// Deactivate chat sets a chat as inactive and clear its history
func ( db sqlitePersistence ) DeactivateChat ( chat * Chat , currentClockValue uint64 ) ( err error ) {
var tx * sql . Tx
tx , err = db . db . BeginTx ( context . Background ( ) , & sql . TxOptions { } )
if err != nil {
return
}
defer func ( ) {
if err == nil {
err = tx . Commit ( )
return
}
// don't shadow original error
_ = tx . Rollback ( )
} ( )
err = db . deactivateChat ( chat , currentClockValue , tx )
return
}
func ( db sqlitePersistence ) deactivateChat ( chat * Chat , currentClockValue uint64 , tx * sql . Tx ) error {
chat . Active = false
err := db . saveChat ( tx , * chat )
if err != nil {
return err
}
2021-05-14 10:55:42 +00:00
return db . clearHistory ( chat , currentClockValue , tx , true )
2020-12-22 10:49:25 +00:00
}
2021-06-07 11:45:06 +00:00
func ( db sqlitePersistence ) SaveEdit ( editMessage EditMessage ) error {
2021-06-08 06:07:45 +00:00
_ , err := db . db . Exec ( ` INSERT INTO user_messages_edits (clock, chat_id, message_id, text, source, id) VALUES(?,?,?,?,?,?) ` , editMessage . Clock , editMessage . ChatId , editMessage . MessageId , editMessage . Text , editMessage . From , editMessage . ID )
2021-06-07 11:45:06 +00:00
return err
}
2021-06-08 06:07:45 +00:00
func ( db sqlitePersistence ) GetEdits ( messageID string , from string ) ( [ ] * EditMessage , error ) {
rows , err := db . db . Query ( ` SELECT clock, chat_id, message_id, source, text, id FROM user_messages_edits WHERE message_id = ? AND source = ? ORDER BY CLOCK DESC ` , messageID , from )
if err != nil {
return nil , err
}
var messages [ ] * EditMessage
for rows . Next ( ) {
e := & EditMessage { }
err := rows . Scan ( & e . Clock , & e . ChatId , & e . MessageId , & e . From , & e . Text , & e . ID )
if err != nil {
return nil , err
}
messages = append ( messages , e )
}
return messages , nil
}
2021-05-14 10:55:42 +00:00
func ( db sqlitePersistence ) clearHistory ( chat * Chat , currentClockValue uint64 , tx * sql . Tx , deactivate bool ) error {
2020-12-22 10:49:25 +00:00
// Set deleted at clock value if it's not a public chat so that
2021-05-14 10:55:42 +00:00
// old messages will be discarded, or if it's a straight clear history
if ! deactivate || ( ! chat . Public ( ) && ! chat . ProfileUpdates ( ) && ! chat . Timeline ( ) ) {
2020-12-22 10:49:25 +00:00
if chat . LastMessage != nil && chat . LastMessage . Clock != 0 {
chat . DeletedAtClockValue = chat . LastMessage . Clock
}
chat . DeletedAtClockValue = currentClockValue
}
2021-03-25 15:15:22 +00:00
// Reset synced-to/from
syncedTo := uint32 ( currentClockValue / 1000 )
chat . SyncedTo = syncedTo
chat . SyncedFrom = syncedTo
2020-12-22 10:49:25 +00:00
chat . LastMessage = nil
chat . UnviewedMessagesCount = 0
2021-05-26 06:38:25 +00:00
chat . UnviewedMentionsCount = 0
2020-12-22 10:49:25 +00:00
err := db . deleteMessagesByChatID ( chat . ID , tx )
if err != nil {
return err
}
err = db . saveChat ( tx , * chat )
return err
}