I specifically stated a FieldIndex, not TextIndex. It is a special case, but when your talking a huge Catalog this could be a lot of extra data. If you want to make it more general, perhaps a PluginIndex could advertise itself as "metadata" capable. When someone adds a metadata field it checks to see if an existing index supports returning of metadata for an RID.
> -----Original Message----- > From: Collector: Zope Bugs, Features, and Patches ... > [mailto:[EMAIL PROTECTED]] > Sent: Thursday, 25 April 2002 6:32 PM > To: djay; chrisw; klm; Brian; chrism; Caseman; _Rejected_ recipient > Subject: [ZC] 365/ 2 Reject "metadata in Catalog is space inefficient" > > > Issue #365 Update (Reject) "metadata in Catalog is space inefficient" > Status Rejected, Catalog/bug low > To followup, visit: > http://collector.zope.org/Zope/365 > > ============================================================== > = Reject - Entry #2 by chrisw on Apr 25, 2002 4:31 am > > Status: Pending => Rejected > > You're making a huge assumption there. > > In many cases, I'm thinking TextIndex being the primary > example here, it's not actually possible, let alone feasible, > to retrieve the originally indexed information from the index itself. > > So your point is kidna invalid ;-) > > cheers, > > Chris > ________________________________________ > = Request - Entry #1 by djay on Apr 25, 2002 3:52 am > > If I create a metadata to be stored so that it is availalbe > in my results, and this metadata is the same as a FieldIndex, > then the data is effectively being stored twice for no > reason. The value of the metadata should just be retrieved > from the index to save space > ============================================================== > > _______________________________________________ Zope-Dev maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )