Surely it should make no difference to caching as they are both GETs?
The first is certainly prettier, if you want URLs like that then ZSQL
methods should be able to help you (read the online zope book), or roll
your own looking at the traverse subpath.
Laurence
Gaute Amundsen wrote:
Hi.
This is because since PlonePAS integration the user password is no
longer stored, instead a hash of the password is stored instead (much
better for security!) This means it is impossible to get the original
password back.
If you do have a need to remind users of their passwords then you must
Gaute Amundsen wrote:
I have been meaning to ask this for a while..
How do people set up the zope development process and servers to work well
with web-designers who use wysiwyg editors like dreamweaver?
snip/
Take a look at deliverance http://openplans.org/projects/deliverance
The other
Use Firefox, it won't time out.
Nothing happened when the browser timed out because the web server had
no way of knowing the browser had timed out.
Laurence
Allen Huang wrote:
I made a python product for a photo album and I have store a lot of
pictures.
But the problem arise when I have
Hi Alan,
I had a similar requirement a few years ago and wrote it up here:
http://plone.org/documentation/how-to/integrate-external-content/
Reading the comments it seems as if someone has made it into a product.
There is also a product called Windowz which uses iframes:
Sounds like you have missed the make install step. You should then be
able to run $SOFTWARE_HOME/bin/mkzopeinstance.py directly to create a
new instance using this version of the software.
Laurence
michael nt milne wrote:
yes, the main instance runs fine but not the new one which was created
Try deleting them with del from python (eg from zopectl debug) rather
than through the ZMI.
Laurence
Ken Ara wrote:
I have a couple of outstanding issues following an
otherwise successful upgrade from Zope 2.7.4 to
2.10.3-final.
One key application used the old DocumentLibrary
product
As an experiment, I started porting zodb to amazon s3 storage a while
ago... http://code.google.com/p/s3storage/
You can use it to start zope, but it makes far too many writes
inefficiently (it took about 15 minutes for zope2 to create all it's
objects on a first start).
Now that ec2 comes
IIRC CookieCrumbler just stores the username:password on the __ac
cookie. You probably need to force it to set another cookie when you
change the password, or move to a different implementation like
plone.session that uses signed cookies and avoids the requirement to
store the password on a
This is only a timeout and nothing to worry about. Either connect
directly to the zope instance to perform the recatalog or just leave it
and wait. You can tell it's done when python is no longer using all your
cpu.
Laurence
Ignacio Valdes wrote:
Hello all, Linux Medical News
On behalf of the Plone and Zope Security Teams I'd like to draw your
attention to a security announcement that has just been published.
This is a pre-announcement only, it does not contain any vulnerability
details. Your sites are a safe today as they were yesterday. However,
as the problem that
On 23 June 2011 23:39, Eric d'Halibut eric.hali...@gmail.com wrote:
Testing an install of Zope on an up-to-date Debian squeeze install, I
get this below. Versions include:
python2.6 2.6.6-8+b1
gcc 4:4.4.5-1
Does this ring any bells with
This is an update on today's security hotfix release.
The fix will be released at 15:00 UTC today, Tuesday 28th June, 2011
(11:00am US EDT.) Updated versions of Zope 2 containing the security
fix will be released at the same time.
For details on which versions of Zope and Plone are affected,
On 28 June 2011 14:40, Norbert Marrale norbertmarr...@yahoo.com wrote:
This should be clarified too: You should, however, make sure that you
are running either Zope 2.10.13 or Zope 2.11.8 and PluggableAuthService
1.5.5, 1.6.5 or 1.7.5
Why must PluggableAuthService (+ its dependencies) even
Last week, the Zope and Plone security teams announced the discovery
of a serious security issue affecting all recent versions of Zope and
Plone, as well as the planned release of a Hotfix to address this
issue to be made today, June 28th at 1500 UTC.
The Plone and Zope security teams are
On 4 July 2011 13:26, Fernando ferna...@cmartins.nl wrote:
Stefan, thanks for your reply.
In the meanwhile I was indeed able to put products in INSTANCE/Products
(Zope 2.13.8). I did not know about that option you mention and I cannot
check it now, but the Products from pypi were being
On 4 July 2011 14:48, Fernando ferna...@cmartins.nl wrote:
On Jul 4, 2011 13:30 Laurence Rowe l...@lrowe.co.uk wrote:
I suggest using http://pypi.python.org/pypi/plone.recipe.zope2instance
(it is not Plone specific) and referring to the Plone documentation
for installing add-ons:
http
You probably need to run it using ZODB 3.8 (i.e. with your Zope 2.10 instance.)
Laurence
On 6 October 2011 13:31, Frank Kauff fka...@biologie.uni-kl.de wrote:
Unfortunately, it's not working:
When starting within the 2.10.4 environment, I get the error
Traceback (most recent call last):
On 6 October 2011 14:40, Frank Kauff fka...@biologie.uni-kl.de wrote:
On 10/06/2011 03:21 PM, Laurence Rowe wrote:
You probably need to run it using ZODB 3.8 (i.e. with your Zope 2.10
instance.)
I think that's what did:
/opt/Zope-2.10/bin/python ../strip_versions.py Data.fs
to read my Data.fs but recent enough to run the conversion script? Can
i get a 2.11 version with ZODB 3.8 from somewhere?
Thanks,
Frank
On 10/06/2011 05:54 PM, Laurence Rowe wrote:
On 6 October 2011 14:40, Frank Kaufffka...@biologie.uni-kl.de wrote:
On 10/06/2011 03:21 PM, Laurence Rowe
Potential security issues should not be discussed on public mailing
lists but submitted to security-respo...@zope.org. Please submit the
full information to that address and do not follow up further on this
list.
Laurence
On 24 October 2011 15:05, Niels Dettenbach n...@syndicat.com wrote:
Dear
On 24 October 2011 22:54, Tres Seaver tsea...@palladion.com wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On behalf of the Zope security response team, I would like to announce
the availability of a hotfix for a vulnerability inadvertently
published earlier today.
On 9 February 2012 05:42, sathya pyt...@zeomega.com wrote:
Greetings,
ram cached pages using the ram cache manager product seems to be a nice way
to improve response times.
As far as I remember it did not work well with ZEO.
Is there any merit to reengineering this product to use
On 23 May 2012 10:56, Richard Harley rich...@scholarpack.com wrote:
Does anyone have a recommendation on how to implement sessioning on Zope 2?
Basically to set browser timeouts for the user so logout after say 20 mins
of inactivity. The difficulty we've had previously is detecting what exactly
On 6 July 2012 14:09, Richard Harley rich...@scholarpack.com wrote:
On Zope 2.10 is there a simple/universal way to only allow python scripts to
be called by DTML methods or other python scripts and not directly TTW?
You can check that the script is not the published object with:
if
On 6 July 2012 16:36, Richard Harley rich...@scholarpack.com wrote:
That works great, thanks. So there is no way to do this across, say, a
folder with hundreds of scripts in without duplicating the code in each
individually?
For one Plone hotfix we took the approach of blacklisting certain
Last week, the Zope and Plone security teams announced the discovery
of a serious security issue affecting all recent versions of Zope and
Plone, as well as the planned release of a Hotfix to address this
issue to be made today, June 28th at 1500 UTC.
The Plone and Zope security teams are
Log message for revision 80958:
tidy up legacy time zones
Changed:
U Zope/trunk/lib/python/DateTime/DateTime.py
U Zope/trunk/lib/python/DateTime/tests/testDateTime.py
-=-
Modified: Zope/trunk/lib/python/DateTime/DateTime.py
whoops, send as subscribed email address.
On 23/10/2007, Laurence Rowe [EMAIL PROTECTED] wrote:
There was no data for it. Trying to retrieve it from the _tzinfo cache
resulted in a KeyError, it's not in pytz.common_timezones or the
_zmap.
'America/Noronha' is not in pytz.common_timezones
Log message for revision 81039:
* Move all timezone usage to use pytz
* Add support to timezone aware datetime conversion
* Correct capitalization of Brazil/DeNoronha
All previous timezone names are tested against the new pytz based timezones.
This test shows that the following zones
Log message for revision 81213:
Revert ISO8601 interpretation to previously broken behaviour (assume GMT
rather than local time as per spec)
Changed:
U Zope/trunk/lib/python/DateTime/DateTime.py
U Zope/trunk/lib/python/DateTime/tests/testDateTime.py
-=-
Modified:
Log message for revision 80912:
The DateTime function may now be invoked with a single argument
that is a datetime.datetime instance. Timezone naive DateTimes may
be converted back to timezone naive datetime.datetime objects with
asdatetime(). All DateTime instances may be converted to a
Log message for revision 80922:
Fix test. According to http://en.wikipedia.org/wiki/ISO_8601
If no time zone information is given with a time, the time zone is assumed to
be in some conventional local time zone.
Changed:
U Zope/trunk/lib/python/DateTime/tests/testDateTime.py
-=-
Log message for revision 89373:
DateTime conversion of datetime objects with non-pytz tzinfo.
Timezones() returns a copy of the timezone list (allows tests to run).
Changed:
U Zope/trunk/doc/CHANGES.txt
U Zope/trunk/lib/python/DateTime/DateTime.py
U
Log message for revision 89375:
DateTime conversion of datetime objects with non-pytz tzinfo.
Timezones() returns a copy of the timezone list (allows tests to run).
(Backport of r89373 from trunk).
Changed:
U Zope/branches/2.11/doc/CHANGES.txt
U
Log message for revision 99493:
don't append Accept-Encoding to Vary header unnecessarily
Changed:
U Zope/trunk/src/ZPublisher/HTTPResponse.py
U Zope/trunk/src/ZPublisher/tests/testHTTPResponse.py
-=-
Modified: Zope/trunk/src/ZPublisher/HTTPResponse.py
Log message for revision 99497:
changelog entry
Changed:
U Zope/trunk/doc/CHANGES.rst
-=-
Modified: Zope/trunk/doc/CHANGES.rst
===
--- Zope/trunk/doc/CHANGES.rst 2009-04-25 23:06:13 UTC (rev 99496)
+++
Log message for revision 99500:
Launchpad #267834: proper separation of HTTP header fields
using CRLF as requested by RFC 2616. (merged 90980, 92625)
Changed:
U Zope/branches/2.10/doc/CHANGES.txt
U Zope/branches/2.10/lib/python/OFS/tests/testRanges.py
U
Log message for revision 99501:
Launchpad #267834: proper separation of HTTP header fields
using CRLF as requested by RFC 2616. (merged 90980, 92625)
Changed:
U Zope/branches/2.11/doc/CHANGES.txt
U Zope/branches/2.11/lib/python/OFS/tests/testRanges.py
U
Log message for revision 99502:
ZPublisher response.setBody: don't append Accept-Encoding to Vary
header if it is already present - this can make cache configuration
difficult. (merged 99493)
Changed:
U Zope/branches/2.10/doc/CHANGES.txt
U
Log message for revision 99503:
ZPublisher response.setBody: don't append Accept-Encoding to Vary
header if it is already present - this can make cache configuration
difficult. (merged 99493)
Changed:
U Zope/branches/2.11/doc/CHANGES.txt
U
Log message for revision 119791:
Branch to experiment with adding a REQUEST property to the application object
and remove the request container
Changed:
A Zope/branches/elro-remove-request-container/
-=-
___
Zope-Checkins maillist -
Log message for revision 119792:
Remove RequestContainer and make app.REQUEST a property looking up the
globalrequest.
This mostly works, but causes two problems:
1. Some very old request using Testing.makerequest are unable to clean up the
globalrequest after themselves, leading to
Log message for revision 119840:
revert change to makesite.txt
Changed:
U
Zope/branches/elro-remove-request-container/src/Products/Five/component/makesite.txt
-=-
Modified:
Zope/branches/elro-remove-request-container/src/Products/Five/component/makesite.txt
Log message for revision 119841:
Add an aq_explicit property to the Application object as it is not longer aq
wrapped.
Changed:
U Zope/branches/elro-remove-request-container/src/OFS/Application.py
-=-
Modified: Zope/branches/elro-remove-request-container/src/OFS/Application.py
Log message for revision 119842:
revert changes to makerequest, need a different approach here
Changed:
U
Zope/branches/elro-remove-request-container/src/Testing/ZopeTestCase/sandbox.py
U
Zope/branches/elro-remove-request-container/src/Testing/ZopeTestCase/utils.py
U
Log message for revision 119843:
Leave makerequest using a RequestContainer to support legacy tests; make
ZopeTestCase set the global request instead. All tests pass.
Changed:
U
Zope/branches/elro-remove-request-container/src/Testing/ZopeTestCase/base.py
U
Log message for revision 121447:
ZPublisher: HTTPResponse.appendHeader now keeps header values to a single
line by default to avoid causing problems for proxy servers which do not
correctly handle multi-line headers.
Changed:
U Zope/branches/2.13/doc/CHANGES.rst
U
Log message for revision 121448:
Merge [121447] to trunk - ZPublisher: HTTPResponse.appendHeader now keeps
header values to a single
line by default to avoid causing problems for proxy servers which do not
correctly handle multi-line headers. (Merged from 2.13 branch.)
Changed:
U
Log message for revision 123200:
New branch for adding parent pointers to Zope
Changed:
A Zope/branches/elro-parent-pointers/
-=-
___
Zope-Checkins maillist - Zope-Checkins@zope.org
https://mail.zope.org/mailman/listinfo/zope-checkins
Log message for revision 123223:
Set parent pointers
Changed:
U Zope/branches/elro-parent-pointers/src/OFS/Application.py
U Zope/branches/elro-parent-pointers/src/OFS/ObjectManager.py
U Zope/branches/elro-parent-pointers/src/OFS/tests/testApplication.py
U
Log message for revision 123224:
Avoid makerequest so app is root object (other tests should also avoid this
to match the new reality.)
Changed:
U Zope/branches/elro-parent-pointers/src/OFS/tests/testCopySupport.py
-=-
Modified:
-1 for removing it. I think it's a cool feature :-)
I like the ability to use a 'blank' SiteRoot (one with a blank base and
path) in conjunction with an access rule to set request variables when I
access my site in through a particular point (eg set the plone_skin
variable when I access my site
Paul Winkler wrote:
On Thu, Apr 07, 2005 at 12:55:09PM +0100, Laurence Rowe wrote:
-1 for removing it. I think it's a cool feature :-)
I like the ability to use a 'blank' SiteRoot (one with a blank base and
path) in conjunction with an access rule to set request variables when I
access my site
As far as I am aware, ZODB will store a list of pointers to the lists of
z objects. What you should be careful of for efficient use of ZODB is
that your list is stored in an efficient way, well if the list is
updated often or long anyway.
When you pack your ZODB does it take up a lot less
See http://www.zope.org/Collectors/Zope/1991
Should be resolved in 2.8 and 2.9
Laurence
On Fri, 12 May 2006 15:07:00 +0100, Erik Dahl [EMAIL PROTECTED] wrote:
I have an object that has a space at the end of its id (I know this is
bogus but I guess its a valid id). its url is:
I actually think TTW schema generation has some validity (so content
types can be easily generated by users). Restricted Python (in python
scripts) just kind of sucks though for being almost python but a little
different. You could keep python code on the filesystem seperate and
just write
I'm trying to work out how to use WSGI with Zope, as I believe that this
is the way to attach a filter to Zope output. However the seem to be
some issues with Zope 2.10.3. Setting use-wsgi on in zope.conf seems to
break Five. The interfaces tab is no longer visible in the ZMI and Plone
stops
Perry wrote:
Tres Seaver schrieb:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
--
2007-05-25T10:19:01 ERROR Zope.SiteErrorLog
http://uniben.waeup.org/campus/students/C172676/study_course/create_level
Traceback (innermost last):
Module Zope2.App.startup, line 173, in
Chris Withers wrote:
Laurence Rowe wrote:
This is just an idea, but zeo is backwards compatible right? So
perhaps you could connect a 2.7 client to a 2.8 zeo server and as long
as you know the oids of the intSets you should be able to load them
and do your conversion.
An interesting idea
This is just an idea, but zeo is backwards compatible right? So perhaps
you could connect a 2.7 client to a 2.8 zeo server and as long as you
know the oids of the intSets you should be able to load them and do your
conversion.
Laurence
Chris Withers wrote:
Dieter Maurer wrote:
The reason
Dieter Maurer wrote:
Laurence Rowe wrote at 2007-8-10 15:34 +0100:
...
Assuming that the 2.7 client won't be able to read 2.8 BTrees
A 2.7 client is able to read *and* write BTrees.
BTrees already exist for a very long time; even very old
Zope versions can read and write them.
I know
Philipp von Weitershausen wrote:
snip /
I believe that datetime is not even importable in TTW code
and datetime objects not accessible in TTW code -- at least,
they have not been until recently...
allow_module('datetime') is all you had to do. Ok, admittedly, pure-TTW
developers who can't or
Quite a lot of zope3 code (zc.datetimewidget for instance) expects to be
able to access request.locale. ZPublisher does not provide this and to
get around the limitation you must manually set request.locale in your
view using Products.CMFDefault.formlib.form.getLocale. This seems
brittle. I
Roché Compaan wrote:
snip /
I use QueueCatalog often and I know how it works. But if an application
requires immediate indexing then QueueCatalog is not a solution.
Sorry if I was unclear but what I'm really asking is if it is possible
to improve the conflict handling of the current indexes
Andreas Jung wrote:
snip /
Just for the logs: I gave up my work on an inplace DateTime migration..
too compliated, too much cruft would have to remain for backward
compatibility. Let's see how we can address the issue in a reasonable
way :-)
To enable an evolutionary approach DateTime -
Dieter Maurer wrote:
Laurence Rowe wrote at 2007-9-26 11:08 +0100:
...
To enable an evolutionary approach DateTime - datetime conversions
must be made round-tripable. This is currently difficult as DateTimes
have a resolution of milliseconds and datetimes a resolution of
microseconds. I
I've been working on this too today (well datetime handling anyway).
Please see my patch at https://bugs.launchpad.net/zope2/+bug/149060
Laurence
Amos Latteier wrote:
Hi,
I wanted to let folks know that I've created the amos-datetime-pytz
branch with my changes.
Please let me know when/if
Lennart Regebro wrote:
On 10/5/07, Laurence Rowe [EMAIL PROTECTED] wrote:
I've tested my patch (datetime.datetime support) against Amos's branch
and it applies cleanly and all tests pass.
Cool! Are there tests to make sure old pickles still work, or do we
know that this is the case for sure
.
Laurence
Laurence Rowe wrote:
I've been working on this too today (well datetime handling anyway).
Please see my patch at https://bugs.launchpad.net/zope2/+bug/149060
Laurence
Amos Latteier wrote:
Hi,
I wanted to let folks know that I've created the amos-datetime-pytz
branch with my changes
Lennart Regebro wrote:
On 10/5/07, Laurence Rowe [EMAIL PROTECTED] wrote:
If anyone thinks it is important I could an explicit upgrade path for
instances with a _millis attribute too (most current instances I would
assume).
I think the code must work with current instances without modifying
I'd like to see the DateTime pytz work and my datetime comapatibility
patch merged as well. (they work fine together).
Laurence
Andreas Jung wrote:
Hi,
any probleme with the following schedule for Zope 2.11:
beta 1 - end of October
RC 1 - around Dec 15th
final - end of the year
Since I am
I've checked in my datetime.datetime conversions patch
Is there any reason that the pytz import is not required? I would like
to add support for conversion to timezone aware datetimes, and would
like to rely on pytz being available.
Laurence
Amos Latteier wrote:
On 10/17/07, Laurence Rowe
Philipp von Weitershausen wrote:
Hanno Schlichting wrote:
Log message for revision 80945:
Moved two implements declarations from Five into the proper classes.
I object to this change. HTTPRequest does not really fulfil the
IBrowserRequest interface, and ObjectManager isn't a real
Lennart Regebro wrote:
On 10/23/07, Laurence Rowe [EMAIL PROTECTED] wrote:
Philipp von Weitershausen wrote:
Hanno Schlichting wrote:
Log message for revision 80945:
Moved two implements declarations from Five into the proper classes.
I object to this change. HTTPRequest does not really
On 23/10/2007, Dieter Maurer [EMAIL PROTECTED] wrote:
Laurence Rowe wrote at 2007-10-23 12:00 +0100:
Lennart Regebro wrote:
...
I guess we need to either actually implement the relevant interfaces,
or split the interfaces into something that can be implemented...
Preferably not too
* Move all timezone usage to use pytz
* Add support to timezone aware datetime conversion
* Correct capitalization of
Andreas Jung wrote:
--On 27. Oktober 2007 18:01:25 -0400 Tres Seaver [EMAIL PROTECTED]
wrote:
DateTime('2006-01-01')._tz
'US/Eastern'
Yeah, that's completely odd.
But standards compliant. The previous behaviour was contrary to the
specification. According to
See the discussion on plone-dev a while ago, link integrity checking
will make Plone 3.0 broken and dangerous. Worth trying with 2.9.8 at least.
Laurence
--On 18. August 2007 21:03:43 +0200 Andreas Jung
[EMAIL PROTECTED] wrote:
--On 23. Juli 2007 08:53:32 +0200 Wichert Akkerman
[EMAIL
approaches to SQLAlchemy integration with Zope:
* z3c.zalchemy (Christian Theune)
* z3c.sqlalchemy (Andreas Jung)
* collective.lead (Laurence Rowe)
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
Martin Aspeli wrote:
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.
I don't
Martin Aspeli wrote:
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
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.
Martijn Faassen wrote:
Hey,
Laurence Rowe wrote:
See pypi or the readme for details, but briefly usage is something like:
engine = create_engine('sqlite:///')
Session = scoped_session(sessionmaker(
... bind=engine, transactional=True, autoflush=True,
... extension
Martijn Faassen wrote:
Hi there (especially Christian),
I think we can work with explicits saves. In many cases the user won't
have to worry about it anyway as the container object will do it for
them (besides making the relation), or this 'query container' we spoke
of will do it for them
Martijn Faassen wrote:
Hi there,
Laurence Rowe wrote:
[snip]
The code would get a session through:
Session = getUtility(IScopedSession, 'my-app')
session = Session()
The drawback is that this is more typing. You do a utility lookup and an
instantiation as opposed to simply importing
Michael Bayer wrote:
On May 7, 2008, at 7:08 AM, Martijn Faassen wrote:
Hi there (especially Christian),
I think we can work with explicits saves. In many cases the user won't
have to worry about it anyway as the container object will do it for
them (besides making the relation), or this
Michael Bayer wrote:
So I will ask you, why can't your application simply have a SalesAddress
and an EngineeringAddress class ? You could even produce them
transparently using a custom __new__() method, i.e.
class Address(object):
def __new__(cls, *args, **kwargs):
if
Laurence Rowe wrote:
Martijn Faassen wrote:
Hey Laurence,
Laurence Rowe wrote:
[snip]
We'll have to stick with scoped sesssions because of threading, but
the engine as local utility pattern should still work.
#myapplication/__init__.py
Session =
scoped_session(sessionmaker(bind
You need an svn checkout of SQLAlchemy until 0.4.6 is released.
Laurence
Andreas Jung wrote:
--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
We need to differentiate between the interface for session configuration
and session usage from an application.
For session usage I think it is fairly simple. We should define an
ISessionContext interface such that:
class ISessionContext(Interface):
def __call__():
return a
Brian Sutherland wrote:
On Fri, May 23, 2008 at 11:39:39PM +0100, Laurence Rowe wrote:
We need to differentiate between the interface for session configuration
and session usage from an application.
For session usage I think it is fairly simple. We should define an
ISessionContext interface
Brian Sutherland wrote:
On Sat, May 24, 2008 at 09:30:18PM +0100, Laurence Rowe wrote:
Brian Sutherland wrote:
On Fri, May 23, 2008 at 11:39:39PM +0100, Laurence Rowe wrote:
We need to differentiate between the interface for session configuration
and session usage from an application
Martijn Faassen wrote:
Laurence Rowe wrote:
We need to differentiate between the interface for session
configuration and session usage from an application.
Session configuration? I'm talking about engine configuration. A session
doesn't need to be configured, except with a session, I think
Martijn Faassen wrote:
Laurence Rowe wrote:
Martijn Faassen wrote:
[snip]
Before we talk more about session configuration, please explain why
we're not talking about engine configuration. :)
Engine configuration is a subset of session configuration. You cannot
have a single ScopedSession
Hermann Himmelbauer wrote:
Am Sonntag, 25. Mai 2008 13:32 schrieb Andreas Jung:
--On 24. Mai 2008 15:44:01 +0200 Hermann Himmelbauer [EMAIL PROTECTED] wrote:
I currently use
SQLAlchemy, but it seems that transactions are managed on the RDB-level
only, which means that the object state is
Hermann Himmelbauer wrote:
Am Montag, 2. Juni 2008 20:04 schrieb Hermann Himmelbauer:
Hi,
In my zope3 tests, I set up some basic test data. After that, I'm calling
transaction.commit(). However, I get the following traceback:
--- snip ---
File copy_reg.py, line
Laurence Rowe wrote:
Hermann Himmelbauer wrote:
Am Montag, 2. Juni 2008 20:04 schrieb Hermann Himmelbauer:
Hi,
In my zope3 tests, I set up some basic test data. After that, I'm
calling
transaction.commit(). However, I get the following traceback:
--- snip
Hermann Himmelbauer [EMAIL PROTECTED]:
Am Dienstag, 3. Juni 2008 12:21 schrieb Laurence Rowe:
Laurence Rowe wrote:
I found it by myself: I registered a zope.sqlalchemy related utility,
which stores an engine (self.engine = create_engine(DSN,...)) and a
scoped session (self.Session
Hermann Himmelbauer wrote:
Hi,
Regarding to the discussion some days ago with the SQLAlchemy Zope3
integration, I still have problems with retrieving the session. I currently
use a utility for the engine, which seems to work well.
However, for retrieving the session, I tried to use the
1 - 100 of 232 matches
Mail list logo