Hi there,

I've done a rudimentary port of the classes in identity.soprovider and
visit over to SQLAlchemy. Things seem to work, but I haven't written
any tests yet.

One thing that I'm having trouble with. SQLAlchemy doesn't have
implied "id" columns like SQLObject, so I added the id column manually
so that the database schema would be exactly the same for
SQLAlchemy-based identity and SQLObject one.

However, I'd also like to write a version that gets rid of the id
column, and uses visit_key, userId, groupId and permissionId as
primary keys. It seems fairly straight forward except for on function
call made from TG into the IdentityProvider, namely validate_identity.

This function is called with user_name, password and visit_id. Seems
to me the visit_id here is not the visit_key (a 40-char string) but
the sqlobject id col (an integer).

If I want to use visit_key instead of this auto-id, do I have to
modify turbogears.identity.something, or can I do this completely in
the IdentityProvider?


Arnar

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to