Make XREF field and index by hand? (OpenInsight Specific)
At 01 JUL 1999 11:33:57AM Oystein Reigem wrote:
I need to make some XREF indexes. Some now, and possibly some every now and then later.
My problem is that I need different word delimiters from the standard set Database Manager and Create_Index use.
(1)
Can I just make my indexes with DM, and afterwards edit the formula (line 8) of the dictionary entry for the XREF fields? DM produces e.g
CALL XREF({field_name},\20FDFCFB2C2E2D5F5C212F28293F2B273B3A22\,"","3")
Can I just go change \20FDFCFB2C2E2D5F5C212F28293F2B273B3A22\ into something else?
(2)
If so, can I also do it programmatically?
In case I might make myself a utility where I can select any table and XREF field and have the utility change the delimiters of the field's formula.
(3)
And what if I instead defined the XREF field "by hand"? I.e make myself a symbolic with a CALL XREF(…) formula and put a Btree index on that? What's there to lose? Is there something else you get for free by using an XREF index?
- Oystein -
At 01 JUL 1999 12:55PM [email protected] onmouseover=window.status=why not click here to send me email?;return(true)", [url=http://www.sprezzatura.com" onMouseOver=window.status=Why not click here to visit our web site?';return(true)]Sprezzatura Group[/url] wrote:
Yes
Yes
No
(Remember to update base dict item as well though with pointer to XREF (Field 22?)
World Leaders in all things RevSoft
At 01 JUL 1999 01:10PM [email protected] - [url=http://www.sprezzatura.com]Sprezzatura Group[/url] wrote:
Actually, what you'd end up with is a BTREE on a symbolic instead of a cross reference on a data field. In most cases this probably won't make a difference. Then end result will still be the same.
Don't forget about setting stop lists. You also might want to create the dictioanry link pointers making this an XRef instead of a Btree. More for completeness really. I would think the only real affect of doing this would be the labels in the index browse windows.
Keep in mind, when you change the delimiters, you'll probably have to rebuild the index.
At 01 JUL 1999 02:19PM Kurt Baker wrote:
Please be aware a Development or Development Ready license is required to create database components (e.g. XREF fields). The implementation (via hand or via program) to create indexes is not provided for in a Runtime.
Kurt
At 01 JUL 1999 05:28PM Marvin wrote:
Is somebody perhaps getting over paranoid about licensing?
At 02 JUL 1999 06:38AM Oystein Reigem wrote:
Andrew and Aaron,
Thanks!
I was tempted to ask you a bonus question since you answered so well, but I'll restrain myself.
- Oystein -
At 02 JUL 1999 06:57AM Oystein Reigem wrote:
Kurt,
This was meant for personal use, so to say, i.e just as tools to produce the kind of indexes I need for my app. Only the finished indexes will be distributed to my clients.
Btw - why the restricted set of delimiters when one defines a cross ref index in Database Manager? Is it really just me that need other delimiters? (Please pass on to the right person.)
(Btw again - for full flexibility one really needs to be able to plug in one's own function instead of XREF. Picking out the words from a string can be more complicated than just distinguishing between delimiter characters and non-delimiter characters. E.g dash can be both a delimiter and non-delimiter in the same data.)
- Oystein -
At 02 JUL 1999 07:46AM Cameron Revelation wrote:
Oystein,
You can plug in your own function. An xref is just a btree on a symbolic.
Cameron Purdy
Revelation Software
At 02 JUL 1999 08:36AM Oystein Reigem wrote:
You can plug in your own function
So the Sprezz boys' replies seemed to imply. What I really said was there is room for improvement in Database Manager's indexing tools. My first wish would be an expanded range of delimiters to choose from. And in more difficult cases the possibility of plugging in any function. (Except I don't really expect more than the former in a tool like DM.)
- Oystein -