On Mon, 30 Jun 2008, Mark Martinec wrote:
> Before we scare everyone away, I'd just like to point out that > as far as varbinary/binary change is concerned, there was no change > in amavisd code between 2.6.0 and 2.6.1. The topic is only about > documentation change, i.e. best practices. If one wants to distinguish > between 'S' and 's' as a value of msgs.content (e.g. as may be seen by > a management application), then binary is a more appropriate data type, > as pointed out by Thomas Gelf. Amavisd does not care about the value > of existing records, it only sets it. Yiu are absolutely right. I had everything up and running before I started to mess with the changes. I just wnated to be uptodate with everything so as to not run into trouble later. > But it does, sid and rid are changed to the same data type as maddr.id : My mistake, I read in one of the mails regarding this topic that an integer would be big enough for most setups, so I thought (stupidly) that changing all of them to an integer would work. But as I said earlier that got me into trouble with the AUTOINCREMENT being reset. So that is not to be recommended. > Looks like the AUTO_INCREMENT counter value was reset after the change > of the table msgs, and started counting from zero again. Not good. > All in all, I am really happy with amavisd-new, thank you! All the best .peter ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php _______________________________________________ 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/
