Seems like the first element of the list of result objects returned by
sqlGetAllotmentArea doesn't define anything called 'AllotmentArea_ID'.
Could it be a case problem? What datbase/db_adaptor are you using?
It is a case problem, which really surprised me because Interbase is not
case
Brian Lloyd wrote:
snip, regarding aq_chain
So nobody (including the various Products I have installed) uses this
incredibly useful attribute. I have numerous places in my source where I
loop through aq_parent attributes.
A good question is whether aq_chain really should be a
To: [EMAIL PROTECTED]
Date: Mon, 19 Mar 2001 19:47:31 -0500 (EST)
From: [EMAIL PROTECTED] (Chris McDonough)
Subject: [Zope-Checkins] CVS: Zope2 - UnTextIndex.py:1.33.2.9
Update of /cvs-repository/Zope2/lib/python/SearchIndex
In directory
Hi,
I wanted to do sonething like this:
dtml-in "objectIds(['DTML Document'])
dtml-call manage_addProperty('foo','bar','string')
/dtml-in
But I am missing the part :-(
I can happily add the property to myself or the folder above (if a DTML
Method is used) but I just cant seem to be
On Mon, 19 Mar 2001, John D. Heintz wrote:
I'm not sure that in the most general case this would solve the problem
either. :-( How do we know when the value (or rather the change in
value) of a property for some Zope object should trigger some method?
This is a definate advantage of
On Tue, 20 Mar 2001, Holger Lehmann wrote:
I wanted to do sonething like this:
dtml-in "objectIds(['DTML Document'])
dtml-call manage_addProperty('foo','bar','string')
/dtml-in
But I am missing the part :-(
I can happily add the property to myself or the folder above (if a DTML
Hi!
I wanted to do sonething like this:
dtml-in "objectIds(['DTML Document'])
dtml-call manage_addProperty('foo','bar','string')
/dtml-in
You might want to use dtml-in "objectValues(['DTML Document'])"
(or objectItems). then just say
dtml-call "manage_addProperty(...)"
or you might
I posted this before but didn't get a reply.
Has any one seen this bug, Or do they know a fix?
ATM this is stopping me using 2.3.1b2 which is a bad thing(tm)
---
Zope Errorr
Zope has encountered an error while publishing this resource.
Error Type: TypeError
Error Value: len() of
Thanks,
dtml-call "_.getattr(this(),_['sequence-item']).manage_addProperty(...)"
worked just like a beauty. I thought I tried that one, but I must have
made a mistake :-)
- Holger
---
catWorkX GmbH Hamburg
Dipl.-Ing. Holger Lehmann
Stresemannstr. 364
22761
"R. David Murray" wrote:
To: [EMAIL PROTECTED]
Date: Mon, 19 Mar 2001 19:47:31 -0500 (EST)
From: [EMAIL PROTECTED] (Chris McDonough)
Subject: [Zope-Checkins] CVS: Zope2 - UnTextIndex.py:1.33.2.9
Update of /cvs-repository/Zope2/lib/python/SearchIndex
In directory
I have written a proposal for the improvement of logging. It builds on
ideas proposed by Chris and Andreas at Digital Creations. It is designed
to augment Zope's enterprise-level capabilities. Please comment!
http://dev.zope.org/Wikis/DevSite/Proposals/NewLoggingAPI
Shane
Is python 2 ready for the upcoming beta? Will the next release of zope win32
come with python 2 or use the installed python if available?
Rgs,
Kent Sin
-
kentsin.weblogs.com
kentsin.imeme.net
___
Zope-Dev maillist -
R. David Murray writes:
To: [EMAIL PROTECTED]
Date: Mon, 19 Mar 2001 19:47:31 -0500 (EST)
From: [EMAIL PROTECTED] (Chris McDonough)
Subject: [Zope-Checkins] CVS: Zope2 - UnTextIndex.py:1.33.2.9
Update of /cvs-repository/Zope2/lib/python/SearchIndex
In directory
In doing some development using Catalogs in 2.3.x, I have run across
some interoperability bugs between the various Catalog classes.
1. Catalog brains are slightly broken when applied agains plain
Catalogs. Looking at __getitem__ in Catalog.py (line 225 and 231 in
2.3.1b2 in particular), the
It's so broken with OR for large datasets that the search results are
virtually meaningless. We see this first-hand on Zope.org (which is now
ANDed after an upgrade) and in most of our consulting projects.
I strongly agree that there should be an easy way to switch textindex
default queries
I cannot reproduce this, Andy, although I'm sure something is up. If it
continues to fail under b3, can you possibly send me a Data.fs that exhibits
the problem?
Sorry,
- C
- Original Message -
From: "Andy Dawkins" [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Tuesday, March 20, 2001
We have a SQL method that works quite nicely by messing around with
__bobo_traverse__ meaning we can pass in long URL's as arguments such as
/SQLMethod/a/b/c, /a/b/c is an argument into ZSQL. This is extremely useful
to use. We do this by overiding __bobo_traverse__.
The problem occurs when we
Actually just notice VirtualHostMonster does the same thing our quick hack
does:
if name in ('manage_main', 'manage_workspace'):
return self.manage_main
Hmm. I guess using before_ or after_traversve hooks would be better than
overriding traverse.
- Original Message
Hello,
I dont know if i'm missing something, or if this is just a style
question. But where do the implimentation specific get/set methods go
(the functions called within a SkinScript for example)? Do i just
stick them anywhere in the aquistion path, or is there some logical
place I should
Casey Duncan [EMAIL PROTECTED] wrote:
"R. David Murray" wrote:
To: [EMAIL PROTECTED]
Date: Mon, 19 Mar 2001 19:47:31 -0500 (EST)
From: [EMAIL PROTECTED] (Chris McDonough)
Subject: [Zope-Checkins] CVS: Zope2 - UnTextIndex.py:1.33.2.9
Update of
I've gotta weigh in here, too; the breakage induced by this change
will be large. Give that what *real* users expect is *neither* a
Boolean "AND" *nor* a Boolean "OR", but instead a DWIM/Googlesque
"affinity" search, I don't think the win is clear enough to warrant
the breakage:
*
21 matches
Mail list logo
