Paul J Stevens schrieb wrote: >> I'd say PostgreSQL does it the right way - a database that throws away >> data without informing anyone is ... hm. > > Spoken like a true believer. But you're right; autoclipping probably > violates sql standards.
It probably violates the idea behind databases :-) >>> I've changed the code in dbmail-message.c a bit to truncate the >>> fieldwidth to a hardcoded 255 width for now. >> >> Is such an overflow possible anywhere else? > > There's at present only one place where inserts into headervalue are > handled. And that's the way I like it. What about the other VARCHAR fields like dbmail_aliases.alias ? It's 100 characters wide. What if someone tries to add an alias like: <long id like some mailing list managers use for subscription>@some.domain.at.the.end.of.the.universe.domain ? dbmail-users will probably tell it worked but MySQL clipped it? No problem a normal user will ever see, but if it could happen ... Thomas -- http://www.tmueller.com for pgp key (95702B3B)
