Your suspicions are correct. There are extra tables created and IBO does
some automatic SQL manipulations for you based on when search criteria is
used on columns you have specified for full-text search operations. These
table and the triggers to maintain them are automatically created for you
and you can also have a service application running on the server machine
which keeps the search tables up-to-date in real time such that your
application requires no special coding to maintain it. I have kept it as
abstracted as possible.

You will notice things if you look in the SQL trace monitor but aside from
that you do most everything else as you normally would in a transparent
fashion.

Hope this helps some,
Jason Wharton
http://www.ibobjects.com

----- Original Message -----
From: "Herbert Sitz" <hsitz@...>
To: <IBObjects@yahoogroups.com>
Sent: Friday, July 11, 2003 10:49 AM
Subject: [IBO] full text search question


> I have a question about the functionality of the full text search
> component in IBO. Currently I'm using DBISAM and I depend on having
> a full text search function that integrates nicely within a query's
> SQL. For example, I can issue a SELECT statement that both queries
> table fields and does a full text search at the same time:
>
> SELECT * from Table where tabledate between '2003-05-01' and '2003-05-
> 31' and textsearch('octopus' in memofield1);
>
> I like the speed and ease-of-use I get when the full-text-search
> functionality is integrated with the SQL in this way.
>
> My question is: what sort of integration with regular SQL does the
> IBO full text search provide? If it doesn't integrate into the SQL
> in the same way as DBISAM's full text search (which I expect may be
> the case), then what process is used to get the results of a SQL
> query joined with the results of a full text search? I want to avoid
> the writing of intermediate tables or anything else that's going to
> slow things down.
>
> Thanks for any help,
>
> Herbert Sitz