Martijn Faassen wrote:
Hi there,
[I originally picked this up on a thread on zope3-users, but this
deserves its own thread here]
There are at least three approaches to SQLAlchemy integration with Zope:
* z3c.zalchemy (Christian Theune)
* z3c.sqlalchemy (Andreas Jung)
* collective.lead
On Tue, Apr 8, 2008 at 11:54 PM, Martijn Faassen [EMAIL PROTECTED] wrote:
All of these are in various states of brokenness. z3c.zalchemy doesn't work
with SQLAlchemy trunk. collective.lead works with it, but only if you check
out a particular branch, and not with sqlite. Quite possibly
Dieter Maurer wrote:
Wichert Akkerman wrote at 2008-4-7 20:45 +0200:
...
Almost surely, Alexander wants to ask why Zope does not allow
non-ASCII characters in ids.
And, in fact, there are only two reasons:
* lazyness of the Zope developpers:
without the restriction to ASCII
= Introduction =
Zope2 allows only a very restricted set of characters in
`ObjectManager` ids -- a subset of the characters which can
be used unescaped in urls. Neither non-ASCII characters are allowed
nor some quite important ASCII characters.
When Zope is used outside the english language
Summary of messages to the zope-tests list.
Period Tue Apr 8 11:00:00 2008 UTC to Wed Apr 9 11:00:00 2008 UTC.
There were 5 messages: 5 from Zope Tests.
Tests passed OK
---
Subject: OK : Zope-2.8 Python-2.3.6 : Linux
From: Zope Tests
Date: Tue Apr 8 21:05:25 EDT 2008
URL:
Below is a first draft of a proposal to cover the features discussed in
this thread. I have bundled a number of loosely related items into the
proposal. I can split them out to separate proposals if that is considered
a better approach.
There are three items which are not resolved in the high
The transaction manager here:
http://svn.plone.org/svn/collective/collective.lead/branches/elro-tpc/collective/lead/tx.py
Has support for TPC and savepoints. It is tested and works. The only
issue with sqlite is that the default in the branch is to use two-phase
commit and sqlite does not
On Apr 9, 2008, at 5:07 AM, kevin gill wrote:
1. IP Extraction
Extract the IP Address from the credentials and store it. Return the
IP Address in the dictionary from extractCredentials().
The value from request._environ['HTTP_X_FORWARDED_FOR'] will be used
if present. otherwise
Martijn Pieters wrote:
On Tue, Apr 8, 2008 at 11:54 PM, Martijn Faassen [EMAIL PROTECTED] wrote:
All of these are in various states of brokenness. z3c.zalchemy doesn't work
with SQLAlchemy trunk. collective.lead works with it, but only if you check
out a particular branch, and not with sqlite.
--On 9. April 2008 14:15:38 +0100 Laurence Rowe [EMAIL PROTECTED] wrote:
@everyone:
If we can all agree to use the same basic session and transaction
management then we should probably push for it to be included as a
sqlalchemy extension module.
I would be happy with such a solution. As
On Tue, Apr 8, 2008 at 5:54 PM, Martijn Faassen [EMAIL PROTECTED]
wrote:
Hi there,
[I originally picked this up on a thread on zope3-users, but this deserves
its own thread here]
There are at least three approaches to SQLAlchemy integration with Zope:
* z3c.zalchemy (Christian Theune)
*
On Wed, Apr 9, 2008 at 9:15 AM, Laurence Rowe [EMAIL PROTECTED] wrote:
The transaction manager here:
http://svn.plone.org/svn/collective/collective.lead/branches/elro-tpc/collective/lead/tx.py
Has support for TPC and savepoints. It is tested and works. The only issue
with sqlite is that
Martijn Faassen wrote at 2008-4-8 23:54 +0200:
...
There are at least three approaches to SQLAlchemy integration with Zope:
Quite possibly
z3c.sqlalchemy has a release that actually works.
The current release is not very robust against some kinds of temporary
problems. When e.g. the
--On 9. April 2008 20:28:18 +0200 Dieter Maurer [EMAIL PROTECTED] wrote:
Martijn Faassen wrote at 2008-4-8 23:54 +0200:
...
There are at least three approaches to SQLAlchemy integration with Zope:
Quite possibly
z3c.sqlalchemy has a release that actually works.
The current release is
Andreas Jung wrote at 2008-4-9 20:34 +0200:
...
Quite possibly
z3c.sqlalchemy has a release that actually works.
The current release is not very robust against some kinds of temporary
problems. When e.g. the database is restarted, z3c.sqlalchemy may
enter a state where all database
Laurence Rowe wrote:
Should one phase commit be set as the default to make it easier to work
with sqlite (and mssql)? Probably yes.
Ideally we'd guess based on the URL scheme but allow it to be set
explicitly, IMHO. Single phase would be the fallback, I guess.
Should the default be for
Martijn Faassen wrote:
Martijn Pieters wrote:
On Tue, Apr 8, 2008 at 11:54 PM, Martijn Faassen [EMAIL PROTECTED] wrote:
All of these are in various states of brokenness. z3c.zalchemy doesn't work
with SQLAlchemy trunk. collective.lead works with it, but only if you check
out a particular
Andreas Jung wrote:
--On 9. April 2008 14:15:38 +0100 Laurence Rowe [EMAIL PROTECTED] wrote:
@everyone:
If we can all agree to use the same basic session and transaction
management then we should probably push for it to be included as a
sqlalchemy extension module.
I would be happy with
--On 10. April 2008 01:57:12 +0100 Martin Aspeli [EMAIL PROTECTED] wrote:
Andreas Jung wrote:
--On 9. April 2008 14:15:38 +0100 Laurence Rowe [EMAIL PROTECTED] wrote:
@everyone:
If we can all agree to use the same basic session and transaction
management then we should probably push for
19 matches
Mail list logo
