there was a "high performance mysql" book a while back , that might offer some non-specific db tips that are just good db design. though i can't remember if it was good or not.
before i move on i'll note two things in a disclaimer - i hate mysql - i love postgres so- if you're looking at legacy stuff , postgres might be the best option because it's the most 'standard' -- so pulling in data from different legacy sources might not involve much work. pg also means you could scale onto systems like vertica or oracle with little extra work. mysql is considerably better now. there is foreign key checking and a "sql standards mode" config options, that makes mysql suck less and behave more standard (like throwing errors when you give it bad data), though i'm not sure how stable the foreign key checks are. a few years ago they were too unreliable for me, and i spent too much time creating application-side foreign key checks, so i just moved to postgres and didn't look back. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
