Milton, > Just fired the release and must say its looking great. > the addition of time_num in msgrcpt is very welcome -- I'm writing an > update script to sync the existing msg&msgrcpt tables with time_num..
SQL cleanup clauses should preferably be able to do without this new field, just perhaps not as quickly. > One question for GUI and per-user purposes..: > Could you also add content-type and sid to "msgrcpt"? Reason i ask is > because joining the maddr table to find sid and rid combinations can > take quite a while in a high volume environment.. ... in the end we could end up with all fields of msgs being duplicated with each recipient in msgrcpt. It goes against a proper database design. You don't need maddr table to get to sid. it is in msgs. A join between msgrcpt and msgs provides each recipient with all information common to a message. I don't think providing a copy of sid and content-type to msgrcpt would make a significant speedup. It is probably a join with maddr that takes time. Mark ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ AMaViS-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/amavis-user AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3 AMaViS-HowTos:http://www.amavis.org/howto/
