On Mon, 2011-12-05 at 16:21 -0500, Chris McDonough wrote:
Tomorrow, I plan to:
- Merge the chrism-py3 branch of zope.sqlalchemy into its trunk.
(http://svn.zope.org/zope.sqlalchemy/branches/chrism-py3/)
to get Python 3 compatibility.
- Once the compat branch is merged, I'll make a 0.7
Tomorrow, I plan to:
- Merge the chrism-py3 branch of zope.sqlalchemy into its trunk.
(http://svn.zope.org/zope.sqlalchemy/branches/chrism-py3/)
to get Python 3 compatibility.
- Once the compat branch is merged, I'll make a 0.7 release of
zope.sqlalchemy.
Any dissent?
- C
On Mon, Dec 05, 2011 at 04:21:51PM -0500, Chris McDonough wrote:
Tomorrow, I plan to:
- Merge the chrism-py3 branch of zope.sqlalchemy into its trunk.
(http://svn.zope.org/zope.sqlalchemy/branches/chrism-py3/)
to get Python 3 compatibility.
- Once the compat branch is merged, I'll
On Sat, 2011-10-01 at 03:28 -0400, Chris McDonough wrote:
On Thu, 2011-09-29 at 15:22 +0100, Laurence Rowe wrote:
I've added chrism as an owner. Before we make a final release I'd like
to revisit the savepoint release branches of transaction /
zope.sqlalchemy. I'll bring this up in another
On Thu, 2011-09-29 at 15:22 +0100, Laurence Rowe wrote:
On 29 September 2011 10:33, Chris McDonough chr...@plope.com wrote:
On Tue, 2011-09-27 at 12:40 -0400, Tres Seaver wrote:
This bootstrap is from Jim's '2' branch of zc.buildout:
On Tue, 2011-09-27 at 12:40 -0400, Tres Seaver wrote:
This bootstrap is from Jim's '2' branch of zc.buildout:
http://svn.zope.org/zc.buildout/branches/2/bootstrap/bootstrap.py?rev=121484view=auto
It is designed to work with Py3k.
I've replaced the bootstrap.py in the chrism-py3 branch
On 29 September 2011 10:33, Chris McDonough chr...@plope.com wrote:
On Tue, 2011-09-27 at 12:40 -0400, Tres Seaver wrote:
This bootstrap is from Jim's '2' branch of zc.buildout:
http://svn.zope.org/zc.buildout/branches/2/bootstrap/bootstrap.py?rev=121484view=auto
It is designed to work with
On 29/09/2011 15:22, Laurence Rowe wrote:
On 29 September 2011 10:33, Chris McDonoughchr...@plope.com wrote:
On Tue, 2011-09-27 at 12:40 -0400, Tres Seaver wrote:
This bootstrap is from Jim's '2' branch of zc.buildout:
On 29 September 2011 16:51, Chris Withers ch...@simplistix.co.uk wrote:
It'd also be great if we could get support for SA 0.7+'s new events
system...
I'm not convinced this will give any benefit. Currently we just require:
Session = scoped_session(sessionmaker(bind=engine,
...
On Mon, 2011-09-26 at 21:47 -0400, Chris McDonough wrote:
In case anyone is interested, I've made a stab at porting
zope.sqlalchemy to Python 3 at
http://svn.zope.org/zope.sqlalchemy/branches/chrism-py3/ . Several
tests still fail. I could use some help fixing them.
To run the test suite:
On 27/09/2011 02:47, Chris McDonough wrote:
In case anyone is interested, I've made a stab at porting
zope.sqlalchemy to Python 3 at
http://svn.zope.org/zope.sqlalchemy/branches/chrism-py3/ . Several
tests still fail. I could use some help fixing them.
Have you tried running the tests by
On Tue, 2011-09-27 at 06:43 +0100, Chris Withers wrote:
On 27/09/2011 02:47, Chris McDonough wrote:
In case anyone is interested, I've made a stab at porting
zope.sqlalchemy to Python 3 at
http://svn.zope.org/zope.sqlalchemy/branches/chrism-py3/ . Several
tests still fail. I could use
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/27/2011 02:01 AM, Chris McDonough wrote:
On Mon, 2011-09-26 at 21:47 -0400, Chris McDonough wrote:
In case anyone is interested, I've made a stab at porting
zope.sqlalchemy to Python 3 at
In case anyone is interested, I've made a stab at porting
zope.sqlalchemy to Python 3 at
http://svn.zope.org/zope.sqlalchemy/branches/chrism-py3/ . Several
tests still fail. I could use some help fixing them.
To run the test suite:
- Create a Python 3.2 virtualenv.
- Install nose into the
I've released zope.sqlalchemy 0.6 with the following changes:
* Implement should_retry for sqlalchemy.orm.exc.ConcurrentModificationError
and serialization errors from PostgreSQL and Oracle.
(Specify transaction=1.1 to use this functionality.)
* Include license files.
* Add
Hi,
In one of my Zope3 projects, I use lovely.remotetask to run specific tasks in
background. These tasks do lengthy database operations via zope.sqlalchemy.
Currently, lovely.remotetask seems to do a Zope3 commit() at the end of the
task, which also does the SQLAlchemy commit.
However, some
This depends on whether you have other resources involved in the
transaction or not. I would assume that you will only have the sql
database committing in the transaction, in which case it makes not a
blind bit of difference if you commit separately or not - just make
sure each individual task is
Am Donnerstag 18 September 2008 07:08:56 schrieb Dieter Maurer:
Brian Sutherland wrote at 2008-9-17 12:33 +0200:
On Tue, Sep 16, 2008 at 02:01:07PM +0100, Laurence Rowe wrote:
Brian Sutherland wrote:
Hi,
I've recently seen a situation where zope.sqlalchemy locked up the
transaction
2008/9/19 Hermann Himmelbauer [EMAIL PROTECTED]:
Am Donnerstag 18 September 2008 07:08:56 schrieb Dieter Maurer:
Brian Sutherland wrote at 2008-9-17 12:33 +0200:
On Tue, Sep 16, 2008 at 02:01:07PM +0100, Laurence Rowe wrote:
Brian Sutherland wrote:
Hi,
I've recently seen a situation
Am Freitag 19 September 2008 11:59:55 schrieb Laurence Rowe:
2008/9/19 Hermann Himmelbauer [EMAIL PROTECTED]:
Am Donnerstag 18 September 2008 07:08:56 schrieb Dieter Maurer:
Brian Sutherland wrote at 2008-9-17 12:33 +0200:
On Tue, Sep 16, 2008 at 02:01:07PM +0100, Laurence Rowe wrote:
2008/9/19 Laurence Rowe [EMAIL PROTECTED]:
2008/9/19 Hermann Himmelbauer [EMAIL PROTECTED]:
Am Donnerstag 18 September 2008 07:08:56 schrieb Dieter Maurer:
Brian Sutherland wrote at 2008-9-17 12:33 +0200:
On Tue, Sep 16, 2008 at 02:01:07PM +0100, Laurence Rowe wrote:
Brian Sutherland wrote:
On Thu, Sep 18, 2008 at 07:08:56AM +0200, Dieter Maurer wrote:
Brian Sutherland wrote at 2008-9-17 12:33 +0200:
On Tue, Sep 16, 2008 at 02:01:07PM +0100, Laurence Rowe wrote:
Brian Sutherland wrote:
Hi,
I've recently seen a situation where zope.sqlalchemy locked up the
transaction
On Tue, Sep 16, 2008 at 02:01:07PM +0100, Laurence Rowe wrote:
Brian Sutherland wrote:
Hi,
I've recently seen a situation where zope.sqlalchemy locked up the
transaction machinery. I'm not sure exactly what happened, but have
attached a failing test for at least one bug which may have
Brian Sutherland wrote:
On Tue, Sep 16, 2008 at 02:01:07PM +0100, Laurence Rowe wrote:
Brian Sutherland wrote:
Hi,
I've recently seen a situation where zope.sqlalchemy locked up the
transaction machinery. I'm not sure exactly what happened, but have
attached a failing test for at least one
Brian Sutherland wrote at 2008-9-16 09:56 +0200:
I've recently seen a situation where zope.sqlalchemy locked up the
transaction machinery. I'm not sure exactly what happened, but have
attached a failing test for at least one bug which may have caused it.
Hopefully it's self explanatory;)
If
Brian Sutherland wrote at 2008-9-17 12:33 +0200:
On Tue, Sep 16, 2008 at 02:01:07PM +0100, Laurence Rowe wrote:
Brian Sutherland wrote:
Hi,
I've recently seen a situation where zope.sqlalchemy locked up the
transaction machinery. I'm not sure exactly what happened, but have
attached a
Hi. I have been working with z3c.dobbin 0.4.1 which uses zope.sqlalchemy
and z3c.saconfig. The last usable state was 4 days ago when changes were
made to release of zope.sqlalchemy where dependencies were changed
without changing the version.
Revision 88953 was made to zope.sqlalchemy but
With an in-memory engine, I seem to lose track of the tables after the
first response.
Turn of events:
1. Request comes in
2. Create some tables
3. Add content and commit transaction
4. Query content
5. Return response
Now...
6. New request comes in
7. Query content
(OperationalError) no
Hi there,
Today I had a discussion with Jasper Spaans about how to go about
improving megrok.rdb, Grok's relational database integration which aims
to integrate Grok with SQLAlchemy. We started developing megrok.rdb at
the Grokkerdam sprint a few weeks ago. We reread the discussion
--On 6. Mai 2008 06:01:14 +0200 Andreas Jung [EMAIL PROTECTED] wrote:
--On 6. Mai 2008 02:26:58 +0100 Laurence Rowe [EMAIL PROTECTED] wrote:
Following discussions with Kapil, Christian and Martin I've developed
zope.sqlalchemy. The aim is to provide a common base for transaction
On Tue, May 06, 2008 at 02:26:58AM +0100, Laurence Rowe wrote:
Any comments appreciated.
It looks very, very good.
--
Brian Sutherland
___
Zope-Dev maillist - Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or
Following discussions with Kapil, Christian and Martin I've developed
zope.sqlalchemy. The aim is to provide a common base for transaction
integration. It does not attempt to define any particular way to handle
database configuration as there is not yet consensus on the best way to
handle it.
--On 6. Mai 2008 02:26:58 +0100 Laurence Rowe [EMAIL PROTECTED] wrote:
Following discussions with Kapil, Christian and Martin I've developed
zope.sqlalchemy. The aim is to provide a common base for transaction
integration. It does not attempt to define any particular way to handle
database
33 matches
Mail list logo
