Use ZCatalog or Catalog in a Python product?
My Python product needs to have its own catalog. Should I use ZCatalog or Catalog? I don't require to expose the catalog in the management interface, so I'm guessing I just need Catalog. Hamish Lawson
From: "Hamish Lawson" <hbl@st-andrews.ac.uk>
My Python product needs to have its own catalog. Should I use ZCatalog or Catalog? I don't require to expose the catalog in the management interface, so I'm guessing I just need Catalog.
If you are cataloging objects in the database, I would definitely recommend subclassing ZCatalog, with it's management interface. You can "hide" it by not showing the tabs, but still letting it be accessible via the /manage_ urls. It will come in handy. If you are indexing something else altogether and the indexes and meta_data columns are fixed, then Catalog will probably work well, and in that case you probably wouldn't subclass fromCatalog, but let the catalog be an attribute on your object. That's my guesses... :-) Best Regards Lennart Regebro Torped Strategi och Kommunikation AB
Lennart Regebro wrote:
If you are cataloging objects in the database, I would definitely recommend subclassing ZCatalog,
That's the biggest mistake I ever made with Squishdot ;-)
with it's management interface. You can "hide" it by not showing the tabs, but still letting it be accessible via the /manage_ urls. It will come in handy.
I'd recommend having a ZCatalog called, say, catalog, as an attribute of your Product's instances, that way, to get to the ZCatalog management screens you can go to: your_prod_instance/catalog/manage ...and you don't have to guess what teh tabs will be renamed to in future Zope versions... cheers, Chris
participants (3)
-
Chris Withers -
Hamish Lawson -
Lennart Regebro