Project Summary

  Analyzed 4 days ago based on code collected 4 days ago.

ActivemodelPython already has tons of SQL-wrappers and ORMs and some are quite good. Nevertheless I started my own. Mainly to see if it is possible to implement the API used in Rails.

Some parts required a lot of tricks and magic metaclasses. But in the end it worked well.

Every model class represents a table in the database. Instances of the class represent rows of the table and the attributes of an instance are the column values of the row.

Unlike other object relationional mappers (ORMs) you do not have to specify the columns in the class. This follows the Don't-Repeat-Yourself principle (DRY).

Additionsally I added query features as seen in Django, SQLAlchemy and SQLObject.

The only supported database at the moment is MySQL but SQLite and other backends will follow probably.

Unlike Rails activemodel currently provides no mechanism for migration or validation.

Please read the README in the wiki for more information.

Please send questions and feedback to henning.schroeder (at) gmail (dot) com

Share

In a Nutshell, activemodel...

 

Activity

30 Day Summary May 16 2013 — Jun 15 2013

12 Month Summary Jun 15 2012 — Jun 15 2013

Community

Ratings

Be the first to rate this project
 
Click to add your rating
 
Review this Project!
 
 
 

Creative Commons License Copyright © 2013 Black Duck Software, Inc. and its contributors, Some Rights Reserved. Unless otherwise marked, this work is licensed under a Creative Commons Attribution 3.0 Unported License . Ohloh ® and the Ohloh logo are trademarks of Black Duck Software, Inc. in the United States and/or other jurisdictions. All other trademarks are the property of their respective holders.