A NOTE has been added to this issue. 
====================================================================== 
http://www.dbmail.org/mantis/view.php?id=280 
====================================================================== 
Reported By:                kc
Assigned To:                
====================================================================== 
Project:                    DBMail
Issue ID:                   280
Category:                   Database layer
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     new
====================================================================== 
Date Submitted:             06-Nov-05 07:55 CET
Last Modified:              06-Nov-05 14:19 CET
====================================================================== 
Summary:                    Encoded subject causes db error when save data to
dbmail_subjectfield as length exceeds 100
Description: 
table dbmail_subjectfield has only 100 char for subjectfield.  In the case
the subject is in utf-8, it need to be encoded which makes it larger than
expected.

Suggest to use "text" instead of varchar(100).  I don't know if there is
any RFC limits subject length line though.

And, shouldn't the subject line be decoded when save it to
dbmail_subjectfield?
====================================================================== 

---------------------------------------------------------------------- 
 paul - 06-Nov-05 14:19  
---------------------------------------------------------------------- 
The code truncates basesubject values to a strlen of 255. The
add_header_tables.pgsql did not reflect the change in the code.

Why do you think the basesubject should be decoded?

Please understand the subjectfield table is used only for
THREAD=orderedsubject and for SEARCH HEADER SUBJECT "somevalue". So we
need to be able to do LIKE and ORDER BY queries efficiently on this field.
Also, I want to keep dbmail as charset/encoding agnostic as possible. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
06-Nov-05 07:55 kc             New Issue                                    
06-Nov-05 14:19 paul           Note Added: 0000951                          
======================================================================

Reply via email to