I think we should create a doc to collect those candidates in an arena
:-D
Till now we have three candidates for default SA:
1. ActiveMapper
2. plain SA definitions
3. TurboEntity
Lee McFadden has checked in [1997] to replace ActiveMapper with plain
SA definitions.
Though plain SA makes SA users feel comfortable that they can take full
advantage of SA with turbogears, it doen't make sense for sqlobject
users that they could do the same thing with half size of code.
Though to use 'turboentity' class to specify the 'tablename' doesn't
make sense to me,
it did a good job for support 'Self-referential' field that SQLObject
did not (without magic
)
Here's a list of how TurboEntity, SQLObject, Active Mapper specify
their table name:
TurboEntity:
class turboentity:
tablename = "tg_user"
SQLObject:
class sqlmeta:
table = "tg_user"
Active Mapper:
class mapping:
__table__ = "tg_user"
Kevin Dangoor wrote:
> On Oct 30, 2006, at 11:06 AM, Jonathan LaCour wrote:
>
> >
> > Also, the web site specifically mentions that it was built with
> > TurboGears in mind, and even includes an example for providing an
> > identity model for turbogears. Very exciting news, and I have already
> > contacted the author about the possibility of supplanting ActiveMapper
> > as the recommended declarative layer for SQLAlchemy.
>
> Shh... we've got a book coming out in a few days that has a chapter
> on using ActiveMapper ;)
>
> Kevin
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
