On Fri, Dec 4, 2009 at 11:25 AM, Jason King <[email protected]> wrote:
> Another question. I'm creating an index, and I've used up all of the > custom1, custom2, etc. variables. There's still a few more things I'd like > to include in the index, but I'm out of room. > > Should I just create dual index's? I can use the same KEY in each, so that > the index's would match. Then, rather than output the CFSEARCH result query > directly, output the results into another query. Then take those two > CFSEARCH queries and join them at the KEY variable. > > Does that seem reasonable/logical? > > Traveling but I'll try to take a look this week. Been a while since I've used this stuff. My gut says once you run out you run out, and I'm pretty sure you can't use the same key in two records, but you could create 'related records' I suppose (maybe that's what you meant). Or still multiple pieces of data in a single custom attribute and separate with a pipe or something along those lines, so e.g. custom1 could be "data1|data2" and you'd know to split that out after you pull the record. -- Matthew Woodward [email protected] http://mpwoodward.posterous.com identi.ca/Twitter: @mpwoodward Please do not send me proprietary file formats such as Word, PowerPoint, etc. as attachments. http://www.gnu.org/philosophy/no-word-attachments.html -- Open BlueDragon Public Mailing List http://www.openbluedragon.org/ http://twitter.com/OpenBlueDragon mailing list - http://groups.google.com/group/openbd?hl=en !! save a network - please trim replies before posting !!
