Hello Guys, Thanks for the info, i did expect that to be the case! I can understand that the architecture is indeed very different.
As an extension to my question then, which DBMS would you guys recommend for stability. We have a small embedded platform which has an unreliable power source. We're currently using SQLite which appears to work pretty well, is that something you would recommend? or is there something else even simpler and more robust? Cheers, Robert On Aug 25, 3:32 pm, Michael Bayer <mike...@zzzcomputing.com> wrote: > On Aug 25, 2010, at 6:26 AM, Rawlins wrote: > > > Hello Guys, > > > Do we have support for CouchDB with SQlAlchemy? Can't seem to find > > much information anywhere so I'm guessing not, just thought I would > > check. > > There's a long term plan to allow plugins that would provide attribute > instrumentation and Session persistence services to objects that are > persisted by a non-SQL database. Such a plugin would need to be written by a > third party for each database backend and querying would also be an ad-hoc > affair. So there's a notion of it but nothing is happening on that front > right now. > > > > > > > Thanks, > > > Robert > > > -- > > You received this message because you are subscribed to the Google Groups > > "sqlalchemy" group. > > To post to this group, send email to sqlalch...@googlegroups.com. > > To unsubscribe from this group, send email to > > sqlalchemy+unsubscr...@googlegroups.com. > > For more options, visit this group > > athttp://groups.google.com/group/sqlalchemy?hl=en. -- You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to sqlalch...@googlegroups.com. To unsubscribe from this group, send email to sqlalchemy+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en.
