Collection specific database action

I think there could be some value in allowing different types to use a different database.  For example, I could have one type that registers with a full-blooded Active Record model, like a User... and then I could use Kilt to administer a table of Users.  And perhaps then I use Devise, who knows.

Still working on this one.
Also, now gets should probably loop through each of the registered databases to find any possible match.