On 5.1.2010 11:32, Alexander Bauer wrote: > My solution for this: > > I store an MD5-Hash of the Message-ID in the Database. > The Hash has always the same length so you have no trouble any more.
This is the way I handle things as well. I've set up the table to have a primary key that consists of the account ID and the message ID's hash fields. Of course, there is a theoretical possibility of collisions, but so far this has never actually happened (I do have some further tests in place in case of a collision occurs, but I believe those have never been executed in production, only during testing). -- Markku Uttula ------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev _______________________________________________ synalist-public mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/synalist-public
