Rails wants to generate the database for me rather than generate the metadata it needs from the db. That's how it's presented by default anyway. I'm sure one ca

Rails wants to generate the database for me rather than generate the metadata it needs from the db. That's how it's presented by default anyway. I'm sure one can use it the other way, it was just never obvious how and I never bothered to pursue it. I shouldn't have to write a class for each db table or maintain other such boilerplate nonsense that easily gets out of sync with the db. The database already has sql which is more powerful and useful than any db framework I've encountered so far. Why would I turn away from that for a framework that has its own dsl? That's crazy. Rails is just one example of such a design, a design I try to avoid as it leads to pain and in my experience terrible architecture and code.