Thomas Gelf schrieb: > The problem is, that there is no way to keep an additional unique key > on the tables. MySQL docs are telling me: > > "...every unique key on the table must use every column in the table's > partitioning expression." (this also includes the table's primary key, > since it is by definition a unique key...)
Is there somewhere a working example DB structure (including example partitions) available? I have really no clue how to clean up my current sub-optimal setup :-( > ... Even if in this > case it could happen that I will get the same mail_id more times (once > per week) it should not do any harm if my "3rd-party-apps" are able > to handle it - is that correct? Or could amavisd-new somehow get into > trouble? Anyone? Cheers & thanks for your help Thomas Gelf ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ 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/
