Home

Attention - the prego interface could be somewhat redesigned due to problem implementing transactions with current approach, and to reduce execution cost a little more. Sorry in advance.

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).

• Installation & configuration
• Migrations
• Executing statements
• Models: how to use the Table class
• Associations, polymorphic associations
• Sync: wait for several callbacks to be all called