Open millenium-codebug opened 3 years ago
hi you are saying it right! we have already opened an internal ticket for this improvement and will be deployed in the next business version so you can expect to have it also in the community version when we see it became a very stable fix (as you know to avoid headaches to the community people we release less often but more stable in this channel) This fix will consider also other impacts because we also have to respect legacy code/implementations regards
There is a roadmap of business version release?
the roadmap of the business release is shared with the partners. about the size of the messages database, have you enabled mysql innodb-file-per-table feature?
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.