[Zope-dev] Turning acquisition off[Zope-dev] Turning acquisition off

2000-12-06 Thread morten
Hi guys, Does anyone know how to disable acqusition ? That is, with a simple method, and not disabling the Acqusition class, something like self.aq_disabled('attribute') . Thanks. -Morten ___ Zope-Dev maillist - [EMAIL PROTECTED]

Re: [Zope-dev] ZCatalog scalability...

2000-12-06 Thread Chris Withers
John Eikenberry wrote: the potential of up to 50,000 entries. Using a ZCatalog for listings This may cause you real problems, especially if there's a 'bulk data load' at any point. Cheers, Chris PS: How's the catalog revamp coming along? Any published ZSearch interface yet?

[Zope-dev] Turning acquisition off selectively.

2000-12-06 Thread Chris Withers
[EMAIL PROTECTED] wrote: That is, with a simple method, and not disabling the Acqusition class, something like self.aq_disabled('attribute') . So kindof the inverse of using Aquisition.Explicit and using the aq_acquire method? What you describe would be really cool... The only workaround

Re: [Zope-dev] Turning acquisition off selectively.

2000-12-06 Thread Robin Becker
I'm almost beginning to understand Acquisition. I can see that it's possible to control the things that my class acquires ie import or ancestor acquisition control, but is it possible to control what other classes acquire from me sort of export/descendant control. -- Robin Becker

Re: [Zope-dev] Turning acquisition off[Zope-dev] Turning acquisitionoff

2000-12-06 Thread Ken Manheimer
On Wed, 6 Dec 2000 [EMAIL PROTECTED] wrote: Does anyone know how to disable acqusition ? That is, with a simple method, and not disabling the Acqusition class, something like self.aq_disabled('attribute') . I believe one way is self.aq_base['attribute']. aq_base gets the unwrapped object

Re: [Zope-dev] Turning acquisition off

2000-12-06 Thread Chris Withers
Ken Manheimer wrote: On Wed, 6 Dec 2000 [EMAIL PROTECTED] wrote: Does anyone know how to disable acqusition ? That is, with a simple method, and not disabling the Acqusition class, something like self.aq_disabled('attribute') . I believe one way is self.aq_base['attribute'].

Re: [Zope-dev] Turning acquisition off

2000-12-06 Thread Ken Manheimer
On Wed, 6 Dec 2000, Chris Withers wrote: Ken Manheimer wrote: On Wed, 6 Dec 2000 [EMAIL PROTECTED] wrote: Does anyone know how to disable acqusition ? That is, with a simple method, and not disabling the Acqusition class, something like self.aq_disabled('attribute') . I

Re: [Zope-dev] Turning acquisition off

2000-12-06 Thread Stefan H. Holek
On Wed, 6 Dec 2000 [EMAIL PROTECTED] wrote: Does anyone know how to disable acqusition ? That is, with a simple method, and not disabling the Acqusition class, something like self.aq_disabled('attribute') . Might this be what you are looking for? http://www.egroups.com/message/zope/45049

[Zope-dev] case insensitive sorts

2000-12-06 Thread Andy McKay
Minor nit and patch: I've found that really for me what users want to see is a case insensitive sort of objects, not the current python case sensitive sort. So that the order of objects from dtml-in and tree is a, A, b, B as apposed to A, B, a, b. Anyway Ive patched dtml-in and dtml-tree to do

Re: [Zope-dev] case insensitive sorts

2000-12-06 Thread Steve Alexander
Andy McKay wrote: Minor nit and patch: I've found that really for me what users want to see is a case insensitive sort of objects, not the current python case sensitive sort. So that the order of objects from dtml-in and tree is a, A, b, B as apposed to A, B, a, b. Anyway Ive patched

Re: [Zope-dev] ZUnit - feedback convocation

2000-12-06 Thread Lalo Martins
On Mon, Dec 04, 2000 at 02:56:26PM -0800, Michel Pelletier wrote: On Mon, 4 Dec 2000, Lalo Martins wrote: The first section is the advocacy section; it will begin with "if you already do unit tests, you may want to skip this section". I'm not sure if the history lesson is out of scope,

Re: [Zope-dev] SQLAlias Memory Leak?

2000-12-06 Thread Dyon Balding
OK, I've had more of a hack at this, and I've narrowed the problem down a little. It appears that any access to an SQLAlias object causes it to not be correctly released. The SQLAlias objects means that you can access column names using a different case to how they are stored in the database.

Re: [Zope-dev] case insensitive sorts

2000-12-06 Thread Andy McKay
Oh yeah for the ZCatalog I have two indexes one upper case and one lower case for some of my classes. No problemo. My area to attack though is the standard views such as the management interface... How's life in Lancaster? Went to school there and grew up in Garstang -- Andy McKay,

Re: [Zope-dev] case insensitive sorts

2000-12-06 Thread Dieter Maurer
Andy McKay writes: what does anyone else think I would not like it. Dieter ___ Zope-Dev maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists -

Re: [Zope-dev] case insensitive sorts

2000-12-06 Thread Rik Hoekstra
Andy McKay wrote: Minor nit and patch: I've found that really for me what users want to see is a case insensitive sort of objects, not the current python case sensitive sort. So that the order of objects from dtml-in and tree is a, A, b, B as apposed to A, B, a, b. Anyway Ive

Re: [Zope-dev] SQLAlias Memory Leak?

2000-12-06 Thread Jon Prettyman
I've seen this as well under DCOracle. -jon Dyon Balding [EMAIL PROTECTED] writes: OK, I've had more of a hack at this, and I've narrowed the problem down a little. It appears that any access to an SQLAlias object causes it to not be correctly released. The SQLAlias objects means that