You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Cuttlefish is focused on transactional email which almost always has a single recipient. So, in most cases we have a single email record which one delivery record attached. We could simplify things, only incurring a little extra overhead if we move all the data from the email table to the delivery table and get rid of the emails table.
So, when a user sends an email to multiple recipients it will get turned into two deliveries with duplicated data. This doesn't seem so bad.
The text was updated successfully, but these errors were encountered:
Cuttlefish is focused on transactional email which almost always has a single recipient. So, in most cases we have a single email record which one delivery record attached. We could simplify things, only incurring a little extra overhead if we move all the data from the email table to the delivery table and get rid of the emails table.
So, when a user sends an email to multiple recipients it will get turned into two deliveries with duplicated data. This doesn't seem so bad.
The text was updated successfully, but these errors were encountered: