Skip to content
sergeych edited this page Aug 16, 2012 · 14 revisions

Historically, prego was created to simplify accees to rails (ActiveRecord) databases, so it borrows its approach from AR but makes it callback-driven and avoids data caching (but caches prepared statements).

Here I'm going to document things that were not covered enough in README.

Clone this wiki locally