garybernhardt/raptor — Issue #19: Records should be called something else
Author: jnicklas
Created: 2011-11-10 07:49:31+00:00
State: open

Sorry I am spamming the issue tracker with a lot of dumb stuff. Just had this realization.

When using a datastore that isn't an ORM/ODM, it doesn't really make sense to talk about records. Since Raptor wants to make no assumption as to how we're structuring our app, and it would make a lot of sense for the "Record" in a lot of cases not to map 1-1 to a database row/document, I think it should have a different name.

Resource is kind of already taken by raptors nomenclature, otherwise that would have been good, maybe Model is better? What do you think?