Thanks Jorge, for taking the time. I realized I did not fully list the operating scenario. Actually, the content to be ignored (*fill-in*) is not known by the server-side in advance, nor can all possible matchable strings be built before hand.
The strings to be used for matches are coming from a text file on the server side. The user can enter anything they wish for the *fill-in* part - the need is to have the match happen post *fill-in* as though it was known by the framework beforehand. Only the user would know at runtime, what would go into *fill-in*. Its neither in the db nor in the file containing the strings to match. The strings in the files are basically just "templates". Thanks, /venkat --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/turbogears?hl=en -~----------~----~----~----~------~----~------~--~---
