Re: 5722-DE1 Text Extender - Enabling column for searching modifies the table?

Ok, as I think about it....

I could create a new SQL table object, then a logical file with the
name of the old physical and the same fields ect...such that the
format level ID is the same.

I think that takes care of problem 1.

Problem 2, I think will be ok as Aldon does support SQL DDL defined objects.

So I think I'll be able to do something like so:
create table &LIB.ITEMMSTR (
 itemnbr  decimal (6,0),
 descr   char(30),
 primary key (itemnbr)
);

call qsys.qcmdexec('call pgm(QDB2TX/DB2TX) PARM(''enable text column
&LIB.ITEMMSTR descr handle myhandle'')'
                              , 0000000087.00000);

Isn't that just lovely.  Maybe I can define QDB2TX/DB2TX itself as a
stored proc....

Wonder how the triggers that the system creates over the table will be
handled by Aldon???  I think that's still going to be a problem as the
trigger names are generated....

I thought the "i" stood for integrated????

Well something to play with this weekend anyway...

Still would like to hear from anyone using the text extender.

Charles

On Thu, Jul 8, 2010 at 11:52 PM, Charles Wilt <charles.wilt@xxxxxxxxx> wrote:

All,

Playing around with the 5722-DE1 Text Extender, hoping to allow for
"fuzzy" searching over the description and other fields in an item
master file.

One problem, when you enable a column for searching, ie. build a text
extender index on that column, the system alters the table structure
by adding a new column to the table of type DB2TEXTH.

Two issues with this:

1) Kind of screws up all the RPG program accessing the file doesn't it?
2) What about the CMS (Aldon in this case)?  I get the distinct
impression that a file so altered isn't going to play nicely with the
CMS.


Has anybody used the text extenders in either scenario?

Thanks!
Charles