spacetaxi wrote:
> I definitly need Identity. I've already implemented an identity > provider which fits my needs, but it's based on SO, as I took > sosmbprovider as a starting point (and I didn't have any TG experience > before). It would not be that hard to switch it to use SA, but I don't > want to switch as long as there are too many issues with SA and other > TG components. And I do want to be able to use all TG features. FYI, there *is* vist/identity implementation that based on SQLAlchemy, see savisit.py/saprovider.py. As noted by others catwalk/model designer doesn't work with SA yet, but *I* don't use them anyway. > > That said SA is still relatively new, and I would not be suprised if > > another breaking api change happens. > > TG has many nice features, but currently it seems to be a little bit > stressful keeping an TG-powered application up-to-date. It seems that > some components (e. g. SA) are just too new. Hmm... You can have a database abstraction API (e.g. such as DatabaseFacade pattern) to insulate your code from SO/SA choice. This may be benefitial in long-term project anyway, regardless of whether you're using an ORM tool or access database directly via DB-API. Max. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
