使用保存点支持将Zope连接到Postgres - ZPsycopgDA的替代方案

时间:2022-10-22 07:22:58

Is there a way to get savepoint support in a Zope connection to Postgres?

有没有办法在与Postgres的Zope连接中获得保存点支持?

I'm currently using ZPsycopgDA, which doesn't support savepoints, and is also hard to install with buildout. Would switching to something like SQLAlchemyDA make things easier?

我目前正在使用不支持保存点的ZPsycopgDA,并且使用buildout也很难安装。切换到像SQLAlchemyDA这样的东西会让事情变得更容易吗?

Background: I've got my users in a postgres database, but when I try look at the history, I get errors about savepoints. That problem is explained here: http://plone.org/products/cmfeditions/issues/46

背景:我的用户在postgres数据库中,但是当我尝试查看历史记录时,我会收到有关保存点的错误。这个问题在这里解释:http://plone.org/products/cmfeditions/issues/46

2 个解决方案

#1


I would recommend asking in the Plone forums: http://plone.org/support

我建议在Plone论坛上询问:http://plone.org/support

I'm not using much relational databases myself, but in general you can use collective.tin and other integration products that hook up SQLAlchemy to Plone for content, or if you want to store everything in a relational database, look at RelStorage.

我自己并没有使用太多的关系数据库,但一般情况下,您可以使用collective.tin和其他集成产品将SQLAlchemy连接到Plone以获取内容,或者如果您想将所有内容存储在关系数据库中,请查看RelStorage。

#2


It turned out that SQLAlchemyDA does seem to support savepoints - at least when I switched to it, it did fix the issue.

事实证明,SQLAlchemyDA似乎确实支持保存点 - 至少当我切换到它时,它确实修复了这个问题。

#1


I would recommend asking in the Plone forums: http://plone.org/support

我建议在Plone论坛上询问:http://plone.org/support

I'm not using much relational databases myself, but in general you can use collective.tin and other integration products that hook up SQLAlchemy to Plone for content, or if you want to store everything in a relational database, look at RelStorage.

我自己并没有使用太多的关系数据库,但一般情况下,您可以使用collective.tin和其他集成产品将SQLAlchemy连接到Plone以获取内容,或者如果您想将所有内容存储在关系数据库中,请查看RelStorage。

#2


It turned out that SQLAlchemyDA does seem to support savepoints - at least when I switched to it, it did fix the issue.

事实证明,SQLAlchemyDA似乎确实支持保存点 - 至少当我切换到它时,它确实修复了这个问题。