Martijn Jacobs wrote at 2005-12-1 01:06 +0100:
...
If some conflict errors occure or for some reason the
objects are not indexed (correctly) or not updated, some important
information is not available for the user. I have experienced alot of
problems with unindexed objects, or not reindexed
Martijn Jacobs wrote:
catalog. The estimation about the amount of objects, with only the leave
nodes as 'SimpleItem' objects will be 30.000.
30,000 is nothing.
The production catalog on one of my projects has 220,000 objects in it,
and I still wouldn't class that as huge.
cheers,
Chris
Martijn Jacobs wrote at 2005-11-29 22:09 +0100:
...
That will be true, but I was wondering where to draw the line, for
example with perfomance issues. All the objects will be in a ZCatalog,
to allow searching for example. But one 'ObjectManager' step less in the
choice what to do with the
Hello Dieter.
This must be a funny classification scheme...
Well, I wanted to have the discussion to be general about this thing
because I can imagine that this issue has been some point of discussion
before, among others, but I will be more specific to explain :
- The structure will have
Martijn Jacobs wrote at 2005-11-29 01:02 +0100:
All those products are different 'types', with different functionality
and different 'roles' as what they represent, so I write different
products for every type. For every object that can contain subobjects
you could derive it from 'Folder'
Hello Dieter.
...For every object that can contain subobjects
you could derive it from 'Folder' (or Object Manager). But when you
derive all these product types from 'Folder' you end up with ALOT of
objects in your database.
It that a problem? It might become one once you
Hello guys!
I have a simple question about the design of hierarchical zope product
structures in Zope 2. For example, you have categories, within
categories you have sub-categories, within sub-categories you have
sub-sub categories, within that you have content items, within content
items
