on my previous email I said ActiveMapper instead of ActiveRecord :)
Kevin Dangoor wrote:
> SQLObject (and Rails' ActiveRecord) may not have as powerful a model
> as SQLAlchemy, but they are super easy to use. If you're creating
> a brand new database, the Active Record pattern can work great.
> ActiveMapper does not (or at least need not) prevent you from growing
> into all of SQLAlchemy's features as you need them. If it lets you
> get to the Table objects, you can make your own Mappers later, if you
> decide you need them.
You can indeed access the tables on your objects if you use ActiveMapper
just by saying MyClass.table. I created ActiveMapper because I wanted
SQLAlchemy to be as easy to use as Rails' ActiveRecord and SQLObject.
That's great I believe ActiveRecord should never obscure the tables to a way you can't access them, if that ever happens will kill the idea and we'll be stuck with SQLObject-like problems again.
Any problems experienced right now with mixing ActiveMapper with plain
SQLAlchemy tables and mappers are bugs, and I would like them fixed.
In the same way, if people find things that they would like added to
ActiveMapper that are missing, I would like them added. I fully admit
that ActiveMapper is definitely experimental at this point but so is
TurboGears' support for SQLAlchemy.
and TG itself :)
The only way for something to move beyond the "experimental" stage is for people to use it, find problems
and deficiencies, and solve them.
yes your right, now that we almost have support for 0.2 I'll probably migrate a couple of things to it, and I'll try to use the ActiveMapper when I can.
In my opinion, plain SQLAlchemy is not an acceptable replacement for
SQLObject in TurboGears.
I believe it is, although some help from ActiveMapper will be welcome for some people but not for everyone.
TG will always have a problem with this kind of thing, we are a framework of the best of the best, and of course they are many best out there :) Kevin's solution for templates was great (although something like that will probably wont apply here) kid is the best but if you need something that kid can't get you (like create plaintext, you can easy get support for it.)
I believe that on the backend in the future the best of breed will be SQLAlchemy, not SQLAlchemy with ActiveMapper.
So Turbogears code should use pure sa, while programs build on top of it can either use ActiveMapper or plain sa.
ActiveMapper should be look as a tool to make TG easier not as a core component.
and of course our docs will show how to use ActiveMapper extensively (all intro tutorials should use it), and then have a section of docs related to using pure sa.
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
