> You can create a single collection contains both File and Path > index entries, but that collection cannot also contain Custom index > entries. This is because while both File and Path index entries > are based on disk files as indexing targets, Custom index entries > are based on database content as an indexing target, so the > configuration of Custom entries cannot coexist in the same collection.
Actually, this is incorrect. You can use database and filesystem content within the same Verity collection if you're using the Verity VDK as opposed to K2. When you search the collection, you can differentiate between database and filesystem results by looking at the key column, which will contain a filesystem path if the result points to a file, or whatever you put in there (presumably a primary key or some custom unique identifier) if the result points to a database record. Dave Watts, CTO, Fig Leaf Software http://www.figleaf.com/ Fig Leaf Software provides the highest caliber vendor-authorized instruction at our training centers in Washington DC, Atlanta, Chicago, Baltimore, Northern Virginia, or on-site at your location. Visit http://training.figleaf.com/ for more information! ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Discover CFTicket - The leading ColdFusion Help Desk and Trouble Ticket application http://www.houseoffusion.com/banners/view.cfm?bannerid=48 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:207884 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
