Just checking on how things are progressing with the SQLAlchemy backend.
I am planning on a fairly large rollout of OpenERP and I would really like to
wait until SQLAlchemy is being used for the ORM - because i am worried that
there might be migration issues if I rollout prior to and then need
Is there a blueprint or a specs doc about this?
we would really like to help you with the development.
are there bottlenecks or issues to start to work on?
No, but once the basics are developped, I can make an announce and call
for contribution. We currently focus on MySQL and PostgreSQL
[quote=fabien]You can follow developments on launchpad:
lp:~openerp-commiter/openobject-server/server-sa/
We hope to release a version within one month. We are not sure we will
integrate data versioning in this version yet. You can use the audit trail
module, that manages changes on
Hello, I'm very interested in the work proposed to use SQLAlchemy for
parts of the OPenERP ORM.
In particular, the addition of data versioning (time dependent data in
fields).
Has this work been started in the trunk or is there a particular branch
I can checkout to see how this is progressing
You can follow developments on launchpad:
lp:~openerp-commiter/openobject-server/server-sa/
We hope to release a version within one month. We are not sure we will
integrate data versioning in this version yet. You can use the audit trail
module, that manages changes on data.
forum-u...@tinyerp.org wrote:
You can follow developments on launchpad:
lp:~openerp-commiter/openobject-server/server-sa/
We hope to release a version within one month. We are not sure we will
integrate data versioning in this version yet. You can use the audit trail
module, that manages
