On 8/30/06, Zarrabeitia <[EMAIL PROTECTED]> wrote:
try SQLAlchemy instead of SQLObject. It can handle too pre-existing database schemes. Take a look at the wiki,
http://trac.turbogears.org/turbogears/wiki/UsingSqlAlchemy
Javier Rojas
I have a database that is currently in use by several apps. It
contains the users authentication data (but no group data or
permissions, until now, all users were equal).
As an added difficulty, not all of the existing tables use an integer
as a primary key (the users table, for instance, uses the username
instead).
try SQLAlchemy instead of SQLObject. It can handle too pre-existing database schemes. Take a look at the wiki,
http://trac.turbogears.org/turbogears/wiki/UsingSqlAlchemy
Javier Rojas
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "TurboGears" group.
To post to this group, send email to turbogears@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/turbogears
-~----------~----~----~----~------~----~------~--~---