On 7/30/06, felciano <[EMAIL PROTECTED]> wrote:
currently the db backend is not as easy to change as other components... for example the templating engine.
but if you look closely as how the support for SQLObject/SQLAlchemy is implemented you can (with a little work) replace the backend with your own as long as you keep the interface nothing should break. (that was the path taken for implementing SQLAlchemy.
Hi --
I like what I see in TG, but am having a hard time figuring out where
to look to understand the dependencies on SQLObject. Has anyone used TG
to connect to a non-SQLObject-based data store, either directly or by
providing a custom model-to-store mapping?
currently the db backend is not as easy to change as other components... for example the templating engine.
but if you look closely as how the support for SQLObject/SQLAlchemy is implemented you can (with a little work) replace the backend with your own as long as you keep the interface nothing should break. (that was the path taken for implementing SQLAlchemy.
but remenber SA support is very new and it's in a transition state, the main goal is to change it not keep both, although probably the interface will stay there and we'll end up with something similar to the view (kid as default, many as options)
although as Damjan said, many TG tools are build knowing that SQLObject is there so many *addons* shouldn't work.
but as I said it can be done, and it isn't rocket science.
basically you will have to replace/add to http://trac.turbogears.org/turbogears/browser/trunk/turbogears/database.py
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
