portal_catalog: Archetypes versus GenericSetup

Dorneles Treméa deo at plonesolutions.com
Tue Apr 17 23:48:01 UTC 2007


Hey Martin,

> > /me will continue to use the AT approach when possible (e.g. when
> > an AT schema is available) and the GS approach when it's not...
> 
> You can't do that (sensible/easily) if you use GS-based configuration of 
> FTIs. the 'index' thing is used when you call installTypes() in an 
> Install.py. With GS, there is no code calling installTypes() (and you 
> probably don't want it to) so there is nothing processing the schema for 
> indexes.

yeah... I just figured that out now... and by the hard way... :-(

> I find the GS approach much more natural and sensible anyway. Indexes 
> are inhrently global things, in that if you add an index it will try to 
> find a value every single object that's being cataloged. Tying it to an 
> AT schema makes it look like it's only for that particular field on that 
> particular object, which is wrong. It also mixes "runtime" code (the 
> schema) and install-support code.

Which means that GS is the preferred way from now and on.

Closed case.

-- 
 ___________________________________________________________________

       Dorneles Treméa · Developer · Plone Solutions · Brazil

   Consulting · Training · Development · http://plonesolutions.com
 ___________________________________________________________________

  Plone Foundation · http://plone.org/foundation · Protecting Plone





More information about the Product-Developers mailing list