Tres Seaver said:
Thanks for taking this initiative, Brad!
Thanks for the encouragement.
Kader got started on this and he came up with a couple of questions:
* The tests for SQLALchemy DA make use of ZopeTestCase. Is that
deprecated? I found a discussion of Zope test runners in zope-dev,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Brad Allen wrote:
Tres Seaver said:
Thanks for taking this initiative, Brad!
Thanks for the encouragement.
Kader got started on this and he came up with a couple of questions:
* The tests for SQLALchemy DA make use of ZopeTestCase. Is that
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Brad Allen wrote:
* The tests were written for SQLALchemy 0.4, which had a
session.save method. SQLAlchemy 0.5 and 0.6 use session.add. Do we
need to maintain support for SQLAlchemy 0.4? I am tempted to make this
new release support only 0.5
I've created a LaunchPad project for the Zope SQLAlchemy DA, and
created a LaunchPad team of people who are interested in maintaining
it. Andreas has been listed as the main driver, and links have been
setup to Andrea's home page, SVN, and PyPI.
https://launchpad.net/zope-sqlalchemy-da
A bug for
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Brad Allen wrote:
I've created a LaunchPad project for the Zope SQLAlchemy DA, and
created a LaunchPad team of people who are interested in maintaining
it. Andreas has been listed as the main driver, and links have been
setup to Andrea's home
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tres Seaver wrote:
Andreas Jung wrote:
Tres Seaver wrote:
Andreas Jung wrote:
Brad Allen wrote:
On Fri, Apr 23, 2010 at 9:44 AM, Brad Allen bradallen...@gmail.com
wrote:
On Thu, Apr 22, 2010 at 11:37 PM, Andreas Jung li...@zopyx.com wrote:
On Thu, Apr 22, 2010 at 11:37 PM, Andreas Jung li...@zopyx.com wrote:
Can this fix be included in the upstream SQLAlchemy DA, so nobody has
to monkeypatch it in?
Sorry - being to busy right now. Please commit the fix yourself and
someone with Zope checkin permissions in the repos and create
On Fri, Apr 23, 2010 at 9:44 AM, Brad Allen bradallen...@gmail.com wrote:
On Thu, Apr 22, 2010 at 11:37 PM, Andreas Jung li...@zopyx.com wrote:
Can this fix be included in the upstream SQLAlchemy DA, so nobody has
to monkeypatch it in?
Sorry - being to busy right now. Please commit the fix
On Fri, Apr 23, 2010 at 10:32 AM, Andreas Jung li...@zopyx.com wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Brad Allen wrote:
On Fri, Apr 23, 2010 at 9:44 AM, Brad Allen bradallen...@gmail.com wrote:
On Thu, Apr 22, 2010 at 11:37 PM, Andreas Jung li...@zopyx.com wrote:
Can this fix
On Fri, Apr 23, 2010 at 11:14 AM, Brad Allen bradallen...@gmail.com wrote:
To install the 'dev' version using buildout, it might look something like
this:
recipe = zc.recipe.egg
eggs = Products.SQLAlchemyDA==dev
Or, you could put it in a version.cfg file which some buildouts use,
[versions]
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Brad Allen wrote:
On Thu, Apr 22, 2010 at 11:37 PM, Andreas Jung li...@zopyx.com wrote:
Can this fix be included in the upstream SQLAlchemy DA, so nobody has
to monkeypatch it in?
Sorry - being to busy right now. Please commit the fix yourself
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Andreas Jung wrote:
Brad Allen wrote:
On Fri, Apr 23, 2010 at 9:44 AM, Brad Allen bradallen...@gmail.com wrote:
On Thu, Apr 22, 2010 at 11:37 PM, Andreas Jung li...@zopyx.com wrote:
Can this fix be included in the upstream SQLAlchemy DA, so nobody
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tres Seaver wrote:
Andreas Jung wrote:
Brad Allen wrote:
On Fri, Apr 23, 2010 at 9:44 AM, Brad Allen bradallen...@gmail.com wrote:
On Thu, Apr 22, 2010 at 11:37 PM, Andreas Jung li...@zopyx.com wrote:
Can this fix be included in the upstream
On Mon, Aug 17, 2009 at 9:24 AM, Maric Michaud ma...@aristote.info wrote:
robert rottermann a écrit :
I do not see any reference to mark_changed
you have to call it before any transaction.commit() to tell the zope
transaction
machinery that it has to commit you changes also.
robert
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Brad Allen wrote:
Maybe I wasn't clear but the patch works well with my existing zsql code.
Andreas,
We are trying out the Zope SQLAlchemy DA at work, and one of our
developers saw the same problem with no commits being generated after
On 17.08.09 16:24, Maric Michaud wrote:
robert rottermann a écrit :
I do not see any reference to mark_changed
you have to call it before any transaction.commit() to tell the zope
transaction
machinery that it has to commit you changes also.
robert
In fact, what I understood is
I do not see any reference to mark_changed
you have to call it before any transaction.commit() to tell the zope transaction
machinery that it has to commit you changes also.
robert
Maric Michaud schrieb:
Hi all,
I wanted to use SQALchemyDA with a standalone Zope 2.11 (we only depends
on
robert rottermann a écrit :
I do not see any reference to mark_changed
you have to call it before any transaction.commit() to tell the zope
transaction
machinery that it has to commit you changes also.
robert
In fact, what I understood is that zope.sqlalchemy, by default, bypasses
the
Maric Michaud schrieb:
robert rottermann a écrit :
I do not see any reference to mark_changed
you have to call it before any transaction.commit() to tell the zope
transaction
machinery that it has to commit you changes also.
robert
In fact, what I understood is that
19 matches
Mail list logo
