quick question. Why remove physmessage? Can't you use it to your
advantage here? The physmessage table already makes sure that multiple
copies of a single message will only be stored as messageblocks once.
You should be able to use this to allow multiple users to use the same
physmessage. Or is there something I'm not taking into account here?
I'm not sure I understand physmessage.
In 1.x, We have 2 unique message ids, message_idnr and unique_id.
messageblks uses message_idnr to associate the storage with the message
record.
i.e. Message <- (1:n) message_blks
in 2.x, we have added physmessage_id in it's own table, with a couple
of other columns that used to be in the messages table. But the
physmessage table isn't mapping anything, it's just splitting off
storage for some values into another table. The real change is that the
messageblks aren't referring to a specific message id, rather the
messages are referring to a 'per unique message sequence' where unique
message means delivered at the same time through the same invocation of
dbmail-smtp.
Message -> (m:n) message_blks
eric
