Robert,

The full text index synchronization component can be put inside of your
transaction context and told to function in conjunction with updates as they
are happening rather than waiting until they are committed. You would just
call the ResyncQueue method (I think that's what I called it) after each
time the index is impacted.

The reason you normally have to wait until your changes are committed is
because typically the synchronization is being run in a seperate service
application in a single separate place. You won't see any changes until they
are committed.

If you cause it to do the sync "on-demand" in your application directly
within the same transaction scope, then everything will still be just fine
whether things are committed or rolled back. The only difference is you will
be rolling back changes to the indexes rather than to the queue tables.

Let me know if you need more assistance.

I'm starting to feel better and so by Monday I should be back in full
motion.

Regards,
Jason Wharton

----- Original Message -----
From: "robert.gilland" <robert.gilland@...>
To: <IBObjects@yahoogroups.com>
Sent: Wednesday, September 01, 2010 10:36 PM
Subject: [IBO] Full Text Search implementation


> In May 2009 I implemented Full Text Search into my application.
>
> My application only used ibobjects for instantiating the Full Text Search
> metadata and initial population of this data. It was my assumption that
> the metadata would do all the work for ensuring the full text searches
> were up to date.
>
> For example:
>
> Application calls INSERT INTO MYDATATABLE;
>
> I expected then the triggers implemented with Full Text Search would then
> take care of the rest.
>
> HOWEVER.
>
> I was wrong it seems.
>
> It seems that the below is the truth:
>
> I call
>
> INSERT INTO MYDATATABLE;
>
> triggers then do a POST_EVENT function which assumes that there is an
> IBOBJECTS connection listening to the database and then the IBOBJECTS
> syncs using the application components.
>
> This was not my understanding and undermines everything I did.
>
> Why couldn't the triggers have done everything?
>
> Is there something I can call that can in a fast way process all Full Text
> Search Queued instructions?
>
> So I can call it just before I call the Full Text Search function every
> time?
>
> Kind Regards,
>
> Robert.
>
>
>
>
>
>
> ------------------------------------
>
> ___________________________________________________________________________
> IB Objects - direct, complete, custom connectivity to Firebird or
> InterBase
> without the need for BDE, ODBC or any other layer.
> ___________________________________________________________________________
> http://www.ibobjects.com - your IBO community resource for Tech Info
> papers,
> keyword-searchable FAQ, community code contributions and more !
> Yahoo! Groups Links
>
>
>