Skip to content

Instantly share code, notes, and snippets.

@jnunemaker

jnunemaker/gist:833256

Created February 18, 2011 04:38
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save jnunemaker/833256 to your computer and use it in GitHub Desktop.
Save jnunemaker/833256 to your computer and use it in GitHub Desktop.
Download ZIP
Why You Should Never Use An ORM
Raw
gistfile1.txt
Why You Should Never Use An ORM
Having built two object mappers in Ruby (MongoMapper and ToyStore), I would like to
throw out a crazy thought. What if, on your next project, you ditch the ORM.
No ActiveRecord. No DataMapper. No anything. Just you and a lower level driver, whispering
sweet nothings into Ruby classes and modules. Could you? Would you? DARE you?
We Rubyists are all about aesthetics, right? We love declaring has_many and belongs_to!
Scope this! Boom! Instant magic happens behind the scenes. Fancy proxies are assembled,
relational algebra is executed, and SQL queries fall from the heavens.
Your ORM does not have to do everything for you. This talk will teach you to:
* Design your interfaces
* Think about your queries
* Understand your databases
* Think differently
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment