2019-11-21 17:19:22 +01:00
|
|
|
CREATE TABLE IF NOT EXISTS chats (
|
|
|
|
|
id VARCHAR PRIMARY KEY ON CONFLICT REPLACE,
|
|
|
|
|
name VARCHAR NOT NULL,
|
|
|
|
|
color VARCHAR NOT NULL DEFAULT '#a187d5',
|
|
|
|
|
type INT NOT NULL,
|
|
|
|
|
active BOOLEAN NOT NULL DEFAULT TRUE,
|
|
|
|
|
timestamp INT NOT NULL,
|
|
|
|
|
deleted_at_clock_value INT NOT NULL DEFAULT 0,
|
|
|
|
|
public_key BLOB,
|
|
|
|
|
unviewed_message_count INT NOT NULL DEFAULT 0,
|
|
|
|
|
last_clock_value INT NOT NULL DEFAULT 0,
|
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 17:25:34 +01:00
|
|
|
last_message BLOB,
|
2019-11-21 17:19:22 +01:00
|
|
|
members BLOB,
|
|
|
|
|
membership_updates BLOB
|
|
|
|
|
);
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
DROP TABLE membership_updates;
|
|
|
|
|
DROP TABLE chat_members;
|
