| I'm using Frontbase's full text index to successfully return rows. The main goal is to allow users to search large-full text columns, returning enterprise objects. I have broken this into three specific requirements as I can't seem to fulfill more than two, regardless of approach.
1) Search for strings in a large text column using Frontbase's full text index (requires SQL such as "...where SATISFIES(full_text_index, search_string)...". 2) Allow user input and pass this as a parameter to the fileSpec for a query. 3) Create or return EOs so as to have relationship information so as to provide key value coding to related tables.
It seems I'm missing something as I can only meet two of the three above at a time. Here are the options performed so far:
A) Using rawRowsForSQL I can do 1 and 2 above. I have converted the results into enterprise objects but do not know how to perform an addObjectToBothSidesOfRelationshipWithKey which would allow access to related objects (such as code tables).
B) Using objectsWithFetchSpecificationAndBindings I can do 2 and 3 above. But EOModeler does not allow the "SATISFIES" term, even when typing it into the fetchSepc in "Use Raw SQL _expression_."
C) Using a stored procedure I can do 1 and 3 above. However, I do not see a way of passing a user-defined search into the store procedure from WebObjects.
Perhaps there is a much better and non-database specific way to quickly search large text fields with features such a stemming, wildcards, etc.
Any help on this matter would be much appreciated.
Regards,
Drew |