Hi I'm using your project since many months and I think that it's better to split the _messages table to reduce the growing speed. In our company we get email with many of us in To,CC or BCC, all user that recive the email generate an entry with the same data in the _messages table, generating thousand of useless rows.
I thought that the following scheme can be helpful:
_messages with all message data (from, to, cc, bcc, hash, etc...)_messages_account with all account related data like (flagged,smownerid,folder,seen,etc...)
This will help to keep the _messages lighter (there is less data to save and can be deduplicated by hash or messageid) and allow faster synchronization of messages since if a message already exist you have only to insert in relation table or sync flag/seen and not perform a insert bigger with the same data multiple times.
This will also impact _messages_attach table in the same way.
Hi I'm using your project since many months and I think that it's better to split the
_messagestable to reduce the growing speed. In our company we get email with many of us in To,CC or BCC, all user that recive the email generate an entry with the same data in the_messagestable, generating thousand of useless rows.I thought that the following scheme can be helpful:
_messageswith all message data (from, to, cc, bcc, hash, etc...)_messages_accountwith all account related data like (flagged,smownerid,folder,seen,etc...)This will help to keep the
_messageslighter (there is less data to save and can be deduplicated by hash or messageid) and allow faster synchronization of messages since if a message already exist you have only to insert in relation table or sync flag/seen and not perform a insert bigger with the same data multiple times.This will also impact
_messages_attachtable in the same way.