On Sonntag 07 Juni 2009 Jonathan Feally wrote: > Any DBA's out there want to chime in on using views vs. a query that > does it all in one? Performance, Best Practice, Pros/Cons??
I would definitely go for a full migration: If I upgrade to 2.4, I want all the DB schema upgraded to 2.4, including the new single instance storage. Otherwise I'd stick do 2.2. The only reason to support the old format would be that 2.2 could be quickly upgraded to 2.4, and then only new messages get the new single instance storage. But then there should be a helper util to convert existing storage on a per-user basis, so I can run it over night/weekend per customer. Something like dbmail-upgrade-si <username> (si for single instance). That would convert all old style messages of that user. That util should also be able to display users still using one or more old style messages, in order to quickly see what's left to be done. If the new format has advantages - and it clearly should have - then everybody should be willing to convert anyway. Converting per-user helps upgrading a 500+ users mailserver in a convenient way, so you can do it within a week or two without any stress. But really everybody should be more or less forced to update the schema to remove the old cruft. Also, have a single upgrade script to upgrade any schema version to the newest would be very appreciated. So people who have an early 2.2 would also get the newset indices etc. A table "version" would be nice to have where a single "dbmail-schema" value is included. Would be good for support also. mfg zmi -- // Michael Monnerie, Ing.BSc ----- http://it-management.at // Tel: 0660 / 415 65 31 .network.your.ideas. // PGP Key: "curl -s http://zmi.at/zmi.asc | gpg --import" // Fingerprint: AC19 F9D5 36ED CD8A EF38 500E CE14 91F7 1C12 09B4 // Keyserver: wwwkeys.eu.pgp.net Key-ID: 1C1209B4 _______________________________________________ Dbmail-dev mailing list [email protected] http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail-dev
