[Zope-dev] what transaction does get_transaction().commit() really commit?

hello, I have a method that reads: 8 def do_something(self): from Zope import DB conn = db.open() conn.root()['name'] = 'value' get_transaction().commit() conn.close() 8 the method can be called from everywhere, and that's the reason

[Zope-dev] Re: AW: jcNTUserFolder

with Zope if it is running in remote user mode. At least, with your patch, one can browse the site anonymously regards, [EMAIL PROTECTED] -Ursprüngliche Nachricht- Von: Jephte Clain [mailto:[EMAIL PROTECTED]] Gesendet: Freitag, 8. Juni 2001 14:25 An: Roesch, Alexander Betreff: Re

[Zope-dev] first zope-2.3.0a2 bug :-)

well, this one is easy. 8-- --- lib/python/Shared/DC/ZRDB/Aqueduct.py.origThu Jan 11 10:59:42 2001 +++ lib/python/Shared/DC/ZRDB/Aqueduct.py Thu Jan 11 10:58:01 2001 @@ -272,7 +272,7 @@

Re: [Zope-dev] zpatterns: how to invalidate the attributecache?

"Phillip J. Eby" wrote: I don't see a need for a mass invalidation operation, just more documentation on these inner workings. :) or the lack of an attribute depencies mechanism :-) if attribute x depends on attribute y from another generic attribute provider, invalidation of y doesn't make y

[Zope-dev] zpatterns: how to invalidate the attribute cache?

Hello, I feel a need to invalidate a dataskin attribute cache after it has been edited, because other objects might want to use the just modified dataskin, but with the new values. Of course, these values come from some attribute providers that should be re-queried. Any thoughts? It seems that

[Zope-dev] Re: zpatterns-0.4.0a5: problem with unregistering transactionals

Jephte CLAIN wrote: I have a case where Transactional._unregister is called without Transactional._register being called, raising an exception in Transaction._unregister and then in ZODB.Transaction.Transaction.__del__, causing Zope to dump core when it is run as a daemon (because python

[Zope-dev] zpatterns-0.4.0a5: problem with unregistering transactionals

hello, I have a case where Transactional._unregister is called without Transactional._register being called, raising an exception in Transaction._unregister and then in ZODB.Transaction.Transaction.__del__, causing Zope to dump core when it is run as a daemon (because python notifies of the

[Zope-dev] several permissions for the same method

Hello, is it possible for a single method, under Zope 2.1.6, to have several permissions? ie __ac_permission__ = ( ('edit my data', 'edit_data'), ('edit others\'s data', 'edit_data'), ) I have the scenario where a user can edit *its* data but not other users's data, unless he has a

Re: [Zope-dev] zpatterns-0.4: defaults attributes, more...

"Phillip J. Eby" a écrit : Try: data=(self.which_one and [self.second_data] or [self.first_data])[0] wow. what a *clever* idea to use [] around self.???_data. I used to write: data=self.which_one and self.second_data or self.first_data but this failed because sometimes self.second_data is a

Re: [Zope-dev] zpatterns: how to specify default values?

"Phillip J. Eby" a écrit : Yes. Name the attributes "class_default_for_X" where X is the attribute name. Thanks very much. This works with the currently release ZPatterns, but alpha5 will go one better and let you create ZClass property sheets that transparently implement this. That is,

[Zope-dev] zpatterns-0.4: creating an item in virtual mode

Hello, I use virtual attribute access to provide access to my SQL database. However, I want to use the Rack.newItem facility to create new records in the database. But it fails because in virtual mode, an item always exists. This patch solves the problem, at least for me --- Rack.py.orig

Re: [Zope-dev] bug in zpatterns-0.4 ?

"Phillip J. Eby" wrote: Nope. The two levels of methods (get/retrieve and new/create) are there to seperate Rack-level concerns from implementation concerns. getItem() and newItem() handle maintenance of Rack-level invariants such as the retrieval cache, while retrieveItem() and

[Zope-dev] bug in zpatterns-0.4 ?

hello, Rack.createItem (low level method) first calls Rack.getItem (higher level method) to check the existence of the item. This causes infinite loop in certain cases. It should (IMHO) call Rack.retrieveItem instead regards, jephte clain [EMAIL PROTECTED

Re: [Zope-dev] zpatterns-0.4a4

at least) They are used for different things. Or it is kept for compatibilty with old applications (at least, LoginManager use the Specialist/Rack paradigm) (Oh Gott, help mine improvink mie English :-) itoo :-) regards, jephte clain [EMAIL PROTECTED

[Zope-dev] DA for postgresql?

don't have the choice -- I have to use PostgreSQL. thanks for any input regards, jephte clain [EMAIL PROTECTED] ___ Zope-Dev maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related

[Zope-dev] zpatterns: win32 dll for DynPersist?

Hello, Has someone compiled the DynPersist dll for win32? if someone has done so, it would be glad to send me a copy by tomorrow. it will help me greatly. TIA, jephte clain [EMAIL PROTECTED] ___ Zope-Dev maillist - [EMAIL PROTECTED] http

[Zope-dev] zpatterns: rackmountables must be of-wrapped

is fine. So: retrieveItem, createItem use vanilla objects getItem, newItem wrap objects before returning them regards, jephte clain [EMAIL PROTECTED] ___ Zope-Dev maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross

[Zope-dev] catlogged specialist and rack

. This, in fact, is a quick hack. remember that all these will be useless when ZPatterns-0.4.0 is out. But I'm fool enough to use evolving software still in infant stage... hope this is useful like it is for me. regards, jephte clain [EMAIL PROTECTED] Searchable.tgz