dude neither SQLObject or SQLAlchemy are supposed to be ODBMS, I think you can infer that from their names.
if you really want an object database check out zope or buzhug something else. Please stop trying to lead things into what they are not. On 11/10/06, Ilias Lazaridis <[EMAIL PROTECTED]> wrote: > > Ilias Lazaridis wrote: > ... > > [In reply to the messages above, which contain typical justifications] > > > projects should really look a little at other implementations: > > > > http://db.apache.org/ojb/ > > > > Providing a _standard_ OO interface is the most important need for the > > whol python domain. > > the OMG standard is not specific to java. > > > The turbogears project would benefit from a possible upgrade path to > > large-scale commercial ODBMS. > > > > http://odbms.org/ > > A subset of a standard can be implemented, this _still_ gives a > migration path to other ODBMS systems. > > - > > I am basicly close before to drop python again (after selecting it in > preference to JAVA), mainly due to the missing persistency system and > _especially_ due to the inability of the community to bundle and > channelize efforts. > > Please realize: > > Not _one_ persistency system can fulfill thos _very_ _basic_ > requirements: > > http://case.lazaridis.com/wiki/Persist#Requirements > > . > > > > > --~--~---------~--~----~------------~-------~--~----~ 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?hl=en -~----------~----~----~----~------~----~------~--~---
