- Zope-Dev - Zope lists

Examples of non-unique XML node ids?
by Martijn Faassen 14 Sep '99

14 Sep '99

Hi there, About XMLDocuments: Does anyone has any example scenarios of when a non unique XML node id occurs? It'd be nice if we could rely on the uniqueness of an XML node id, but apparently sometimes they're not. Stupidly enough I can't come up with a scenario that will *cause* a node id to be duplicated, and I wonder if anyone else has a clue. If I can see the scenarios I'll try to hack the XMLDocument source so that each node has an unique id (in a single XML Document) at all time. Regards, Martijn

1 0

RE: [Zope] Need a list of words not indexed by Catalog
by Terrel Shumway 14 Sep '99

14 Sep '99

near the end of lib/python/SearchIndex/TextIndex.py is a list called 'stop_words' [Zope Dev] It would be good to move this out of the .py file into an editable, internationalizable resource file. -----Original Message----- From: Jason Spisak [mailto:webmaster@hiretechs.com] Sent: Monday, September 13, 1999 9:31 AM To: zope(a)zope.org Subject: [Zope] Need a list of words not indexed by Catalog Can we get a public list of the words not indexed by the Catalog? I just spent a few hours being tortured trying to find out why a guy in the Datbase of 10,000 whose name is 'Max Many', doesn't come up on a last name search, and guess what, the Catalog doesn't index his last name. The word 'many'. Suprize! This is the third gotcha word we've expericened (don't try to find C/C++ in a document) and it's makes people doubt the software. (I explain about the size of indexes and such, and I understand it, but every surprise word you can't find is another step backward.) You might publish a list of words you'll never find in the Catalog. Just in case one of them happens to be a very big part of someone's business. All my best, -- Jason Spisak webmaster(a)hiretechs.com _______________________________________________ Zope maillist - Zope(a)zope.org http://www.zope.org/mailman/listinfo/zope (To receive general Zope announcements, see: http://www.zope.org/mailman/listinfo/zope-announce For developer-specific issues, zope-dev(a)zope.org - http://www.zope.org/mailman/listinfo/zope-dev )

3 2

RE: [Zope-dev] Multiple inheritance woes
by Rik Hoekstra 13 Sep '99

13 Sep '99

> -----Original Message----- > From: zope-dev-admin(a)zope.org [mailto:zope-dev-admin@zope.org]On Behalf > Of Martijn Pieters > Sent: Friday, September 10, 1999 10:24 AM > To: Phillip J. Eby; Zope-dev(a)zope.org > Subject: Re: [Zope-dev] Multiple inheritance woes > > > At 20:05 09/09/99 , Phillip J. Eby wrote: > >At 02:54 PM 9/9/99 +0200, Martijn Pieters wrote: > > >At 14:33 09/09/99 , Rik Hoekstra wrote: > > >> > > > >> > I define a baseclass derived from CatalogAware and DTMLMethod: > > >> > > > >> > class Base(CatalogAware, DTMLMethod): > > >> > def index_object(self): > > >> > # check a few things I want to know about > > >> > # before indexing, maybe even not allowing > > >> > # the indexing > > >> > CatalogAware.index_object(self) > > >> > > > >> > > > >> > > >>A shot in the dark: Shouldn't this be > > >>CatalogAware().index_object(self)? At least this explicitly > > >>instanciates CatalogAware and stops raising TypeErrors. But I'm not > > >>sure this completely solves your problem > > >> > > >>Rik > > > > > >Sorry, you missed =). In normal python this would work, but as Philip > > >pointed out, when using Acquisition and ExtensionClasses, things are > > >different, and throw the Python interpreter off. > > > > > > >Actually, no, it wouldn't, because then you'd get a different TypeError, > >this one for having passed too many arguments to the > index_object() method. > > And besides, you don't want to call another object's index_object() > >method, you want to call an overridden version of *your* index_object() > >method. > > Heh, why does noone ever understand what I am saying =). I ment that _my_ > code would normally work in Python. I wasn't commenting on Rik's. > There is > a reasonable change I might meet him one day. After all, he's > only about an > hours drive away. =) > You bet :-\ (But I've learnt my lesson - I'll never post so quick again) Rik

5 4

ZClass superclassing DTML Document
by Jason Spisak 13 Sep '99

13 Sep '99

Zopifites, I have posted this question before to no avail and submitted it to the collector. I probably didn't phrase it succinctly enough so I'll try again.:^) I have a ZClass that uss DTML Document as a Base Class. When I create an instance of it, the 'id' property shows up in the management interface, but doesn't show up with a <dtml-var id> inside itself, or in the tree tag. This same code worked in beta3 and 4 then it shanked in beta 5 and is still shanked. Any ideas? -- Jason Spisak webmaster(a)hiretechs.com

1 0

RE: [Zope-dev] ZClass superclassing DTML Document
by Michel Pelletier 13 Sep '99

13 Sep '99

> -----Original Message----- > From: Jason Spisak [mailto:webmaster@hiretechs.com] > Sent: Monday, September 13, 1999 10:02 AM > To: zope-dev(a)zope.org > Subject: [Zope-dev] ZClass superclassing DTML Document > > > Zopifites, > > I have posted this question before to no avail and submitted it to the > collector. I probably didn't phrase it succinctly enough so I'll try > again.:^) > > I have a ZClass that uss DTML Document as a Base Class. > When I create an instance of it, the 'id' property shows up in the > management interface, but doesn't show up with a <dtml-var id> inside > itself, or in the tree tag. This same code worked in beta3 and 4 then > it shanked in beta 5 and is still shanked. Any ideas? Try <dtml-var document_id> -Michel

2 1

RE: [Zope] Need a list of words not indexed by Catalog
by Michel Pelletier 13 Sep '99

13 Sep '99

> -----Original Message----- > From: Jason Spisak [mailto:webmaster@hiretechs.com] > Sent: Monday, September 13, 1999 12:31 PM > To: zope(a)zope.org > Subject: [Zope] Need a list of words not indexed by Catalog > > > Can we get a public list of the words not indexed by the Catalog? You asked for it: stop_words=( 'am', 'ii', 'iii', 'per', 'po', 're', 'a', 'about', 'above', 'across', 'after', 'afterwards', 'again', 'against', 'all', 'almost', 'alone', 'along', 'already', 'also', 'although', 'always', 'am', 'among', 'amongst', 'amoungst', 'amount', 'an', 'and', 'another', 'any', 'anyhow', 'anyone', 'anything', 'anyway', 'anywhere', 'are', 'around', 'as', 'at', 'back', 'be', 'became', 'because', 'become', 'becomes', 'becoming', 'been', 'before', 'beforehand', 'behind', 'being', 'below', 'beside', 'besides', 'between', 'beyond', 'bill', 'both', 'bottom', 'but', 'by', 'can', 'cannot', 'cant', 'con', 'could', 'couldnt', 'cry', 'describe', 'detail', 'do', 'done', 'down', 'due', 'during', 'each', 'eg', 'eight', 'either', 'eleven', 'else', 'elsewhere', 'empty', 'enough', 'even', 'ever', 'every', 'everyone', 'everything', 'everywhere', 'except', 'few', 'fifteen', 'fifty', 'fill', 'find', 'fire', 'first', 'five', 'for', 'former', 'formerly', 'forty', 'found', 'four', 'from', 'front', 'full', 'further', 'get', 'give', 'go', 'had', 'has', 'hasnt', 'have', 'he', 'hence', 'her', 'here', 'hereafter', 'hereby', 'herein', 'hereupon', 'hers', 'herself', 'him', 'himself', 'his', 'how', 'however', 'hundred', 'i', 'ie', 'if', 'in', 'inc', 'indeed', 'interest', 'into', 'is', 'it', 'its', 'itself', 'keep', 'last', 'latter', 'latterly', 'least', 'less', 'made', 'many', 'may', 'me', 'meanwhile', 'might', 'mill', 'mine', 'more', 'moreover', 'most', 'mostly', 'move', 'much', 'must', 'my', 'myself', 'name', 'namely', 'neither', 'never', 'nevertheless', 'next', 'nine', 'no', 'nobody', 'none', 'noone', 'nor', 'not', 'nothing', 'now', 'nowhere', 'of', 'off', 'often', 'on', 'once', 'one', 'only', 'onto', 'or', 'other', 'others', 'otherwise', 'our', 'ours', 'ourselves', 'out', 'over', 'own', 'per', 'perhaps', 'please', 'pre', 'put', 'rather', 're', 'same', 'see', 'seem', 'seemed', 'seeming', 'seems', 'serious', 'several', 'she', 'should', 'show', 'side', 'since', 'sincere', 'six', 'sixty', 'so', 'some', 'somehow', 'someone', 'something', 'sometime', 'sometimes', 'somewhere', 'still', 'such', 'take', 'ten', 'than', 'that', 'the', 'their', 'them', 'themselves', 'then', 'thence', 'there', 'thereafter', 'thereby', 'therefore', 'therein', 'thereupon', 'these', 'they', 'thick', 'thin', 'third', 'this', 'those', 'though', 'three', 'through', 'throughout', 'thru', 'thus', 'to', 'together', 'too', 'toward', 'towards', 'twelve', 'twenty', 'two', 'un', 'under', 'until', 'up', 'upon', 'us', 'very', 'via', 'was', 'we', 'well', 'were', 'what', 'whatever', 'when', 'whence', 'whenever', 'where', 'whereafter', 'whereas', 'whereby', 'wherein', 'whereupon', 'wherever', 'whether', 'which', 'while', 'whither', 'who', 'whoever', 'whole', 'whom', 'whose', 'why', 'will', 'with', 'within', 'without', 'would', 'yet', 'you', 'your', 'yours', 'yourself', 'yourselves', ) This is defined in lib/python/SearchIndex/UnTextIndex.py and TextIndex.py. ZCatalog uses UnTextIndexes. I believe confera uses TextIndexes. This list is obviously not going to work for lots of applications. What if you want to search for words like 'six' and 'five'? What if your indexing python code and want to find all ocourances of 'while' and 'for'? What if your indexing French or German? The reason why we have these as stop words is because, for most (English) 'documents' (meaning large bodies of text), these are the most common words encounterd, and have a higher chance of being in a document than not being in a document. The technical reasons get into the very precise and voodooish concepts of relevance, precision, and result set size. This is very deep stuff. Suffice to say, without stop words indexes grow huge, so clip this list at your own risk, and be aware that taking out 'Many' may improve your ability to index your employees, it may also drasticly reduce the relevance and precision while increasing the size of your result set for a different 'kind' of text corpus. > I just spent a few hours being tortured trying to find out > why a guy in > the Datbase of 10,000 whose name is 'Max Many', doesn't come up on a > last name search, and guess what, the Catalog doesn't index his last > name. The word 'many'. Suprize! This is the third gotcha word we've > expericened (don't try to find C/C++ in a document) and it's makes > people doubt the software. (I explain about the size of indexes and > such, and I understand it, but every surprise word you can't find is > another step backward.) The current TextIndexing machinery was intended to be used from a document-centric standpoint. The need to text index small values was not considered way back when the first TextIndex was written. Given the amount of feedback we have recieved on this, it is obviously on our radar. -Michel

2 1

Parse.
by Juan Javier Carrera Obrero 13 Sep '99

13 Sep '99

Hi ! We are using Zope 2.1.6 for Windows NT Server, and Oracle 8i as RDBMS. When the ZSQL methods are runned, the values of the parameters of the SQL query are remplaced by Zope before sending the query to the Oracle database jet (it does not the "parse"). Thus, if two users runs the same query but with different parameters, it is considered as two different queries because the values of the parameters of the ZSQL method are remplaced firstly. When it is realized by more users with diferent parameters, the Oracle's cache is fulling quickly and it is overing. Do exists any way for sending the query of the ZSQL method and theirs parameters, trying that the values of the parameters was remplaced in the database jet, and no previously. Perhaps, it was a ODBC problem, or the Zope code does not allow it. I do not know it. Any body can help me ? Thanks. JUAN JAVIER CARRERA OBRERO e-mail: jcarrera(a)uco.es

1 0

Re: [Zope-dev] Caching
by Christopher Petrilli 13 Sep '99

13 Sep '99

> In ROXEN (RXML); There is a tag line where by you can cache certain content > within the <CACHE> brackets. Is there something similar within Zope? What has been thought of is doing more "rendered caching" (i.e. cache rendered results, thereby short-circuiting the DTML process). This could be very advantageous, but gets into a lot of issues of management of the cache which is non-trivial (Vignette, one of our competitors that does "consultant-ware" has several patents on it), so... patches accepted. Note that performance will be one of our "watch words" in the coming months. Chris -- | Christopher Petrilli Python Powered Digital Creations, Inc. | petrilli(a)digicool.com http://www.digicool.com

2 1

Caching
by Paul Mokbel 12 Sep '99

12 Sep '99

In ROXEN (RXML); There is a tag line where by you can cache certain content within the <CACHE> brackets. Is there something similar within Zope? This is how it could be implemented: "  ", where foo bar can be an SQL call.. This can be useful for Message Boards as an example. Thanks, /* "There are two major products that came out of Berkeley: LSD and Unix. We don't believe that to be a coincidence. " -BSD fortunes Paul Mokbel */

1 0

Re: [Zope-dev] Using ZODB standalone
by Phillip J. Eby 11 Sep '99

11 Sep '99

At 02:10 PM 9/11/99 -0400, A.M. Kuchling wrote: >I'm experimenting with using ZODB3 to store a tree of objects, but >don't understand what I'm doing. My expectation is that the amount of >memory used should be bounded, because objects should be flushed from >the cache when they haven't been accessed in a while. Instead, the >Python process grows continually. This should be expected, as FileStorage objects keep an index mapping persistent ID's to file seek positions. Even though the cache should be flushed of the objects themselves, the index will grow with each commit of newly created objects. Thus, memory consumption will grow by at least 32 bytes per object, and probably more, since there is overhead for the mapping object itself when it refactors itself as it grows, and it may cause some memory fragmentation as well. This memory size will never be reduced by much (unless objects are deleted and the DB packed) because any process opening the FileStorage will build up the exact same index upon startup. If you plan on having a million-object DB, plan on having 32-64M of RAM available just for OID indexing. It is probably possible to cut this overhead by having FileStorage use a custom-built mapping object written in C specifically designed for FileStorage's needs, but I have not tried anything like this yet.

1 0