mirror of
https://github.com/status-im/status-go.git
synced 2025-01-25 22:19:51 +00:00
fd49b0140e
* 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.
19 lines
543 B
SQL
19 lines
543 B
SQL
-- Drop any previously created user_messages table.
|
|
-- We don't need to stay backward compatible with it
|
|
-- because it's not used anywhere except for the console client.
|
|
DROP TABLE user_messages;
|
|
|
|
CREATE TABLE IF NOT EXISTS user_messages (
|
|
id BLOB UNIQUE NOT NULL,
|
|
chat_id VARCHAR NOT NULL REFERENCES chats(id) ON DELETE CASCADE,
|
|
content_type INT,
|
|
message_type INT,
|
|
text TEXT,
|
|
clock BIGINT,
|
|
timestamp BIGINT,
|
|
content_chat_id TEXT,
|
|
content_text TEXT,
|
|
public_key BLOB,
|
|
flags INT NOT NULL DEFAULT 0
|
|
);
|