Hi Cedric, taking it to the list...
> About headers: It seems you have the same in dbmail > https://github.com/pjstevns/dbmail/blob/master/sql/postgresql/create_tables.pgsql#L236 More or less. DBMail uses single-instance storage both on message parts (attachments) and header values. > But we can think about storing raw part of the header in an other > field and just fill electronic_mail.header with interesting headers. > But indeed I don't see the issue. It's about storage and search. Don't store headers if you don't need them. That was/is a design flaw in DBMail I'm warning against. > About digest: It is the same design as for attachments. I don't see anything about attachments in your design. In dbmail the digest is used only as a quick lookup key for attachments and headervalues. Not to prevent collisions. > About address and subject: indexing doesn't require a limit (except > for MySQL but there are already a lot of issue with it). So we will > use a varchar (without limit). For the 8 bit, I don't know perhaps we > could store it in base64. Storing as text is fine, but recoding into the proper encoding used on the field can be a pain. You won't believe the amount of crap people sent in mail, esp UTF7 encodings can be misleading. -- ________________________________________________________________ Paul J Stevens pjstevns @ gmail, twitter, skype, linkedin * Premium Hosting Services and Web Application Consultancy * www.nfg.nl/[email protected]/+31.85.877.99.97 ________________________________________________________________ -- [email protected] mailing list
