Michael Bayer wrote: > this is the whole point of the Data Mapper pattern; in a nutshell, > its better than any Active Record pattern. :) its SQLAlchemy's > primary design and really not all that hard. When you use > ActiveMapper its just giving you a thin layer of "shortcut" on top of > things SA does just fine without it.
Michael is absolutely right Sanjaya! ActiveMapper exists for things that are easily expressed in the Active Record pattern. In this case, you would be better off with the Data Mapper pattern. There are many problems that can be solved effectively with Active Record (and thus ActiveMapper), and there is nothing stopping you from using both patterns in your projects. SQLAlchemy is designed to handle *all* cases, which is exactly why I love it! I just created ActiveMapper so that the simple cases would be a bit simpler to express, and to try and inspire people to move over from SQLObject to the promised land ;) Good luck. -- Jonathan LaCour http://cleverdevil.org ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Sqlalchemy-users mailing list Sqlalchemy-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sqlalchemy-users
