For the messageblks to mimeparts migration - I don't really care when it is dropped. So 2.5 is a possibility. As long as 2.4 has a check if table exists at daemon startup so that the code to read from that table is completely skipped if absent. I think that once that functionality is there, the create_tables should no longer include it. Optionally, a config file option that disables reading from the messageblks table. If the value is missing, then it will work as designed now. Once the table is dropped from the code, that option will go unused.
As far as a simpler schema, using the views will suffice for now, and they can be dropped very fast if we go back to a single all-in-one query later. Since we are adding views to do the header 3-way join, why not create a view for search that doesn't have the where headername= and then provide the where headername= in the search function? Call it dbmail_search_header or something like that. I only see one outstanding issue, and that is the patch I sent you to finish dropping the auto_* tables usage in the code. -Jon -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. _______________________________________________ Dbmail-dev mailing list Dbmail-dev@dbmail.org http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail-dev
