This type of case/switch will not be accepted in Apartment. It's pretty explicitly going against OO. I'd prefer to have some sort of interface that the persistent `persistent_schemas` object responds to. I'd be fine with either an array OR proc that can be called. That would allow the user to implement it in any way they desire.

Something like the `String` example for instance seems pretty ridiculous to me. I don't think developers are so lazy that they *have* to pass in a string. They can just call `split` on their own, it's not Apartment's responsibility.