John Lavoie wrote: > -As my database is already defined, I don't see any advantages to > ActiveMapper. Am I wrong?
If you are working against an existing database, and just autoloading, then ActiveMapper doesn't make any sense for you to use, and offers you no advantage over straight SQLAlchemy. I largely wrote ActiveMapper just to support a more SQLObject-like pattern of defining your model. Its been a successful experiment, in my mind, and I use it in several projects today. There are plenty of circumstances in which its a useful way to do things, but a lot of situations where it doesn't really fit. Also, as Karl said, I haven't really had the time to maintain the project to my liking. That being said, I find it fairly comparable to SQLObject already, and am actively looking for people to help enhance ActiveMapper. -- Jonathan LaCour http://cleverdevil.org --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/turbogears -~----------~----~----~----~------~----~------~--~---
