 |
 |
Archives of the TeradataForum
Message Posted: Wed, 14 Feb 2007 @ 10:21:06 GMT
| Subj: | | Re: Accent Insensitive Matches |
| |
| From: | | Mario Galante |
| | No, that would not take anything "extremely complex" (esthetically non-pleasing at the most) and the queries would not be much slower than
the ones with UDF. You surely do not expect a few lines of C in the UDF (and that's what they are) to compete with the internal conversion
routines already present in the database, don't you? And you can be smart and selective and only convert when there is something to convert,
etc. | |
Victor, I was kind of skeptical, but you know what? After a few preliminary tests using a limited number of characters to replace, the
performance is really not that bad. Of course, as you mention, the resulting SQL code is horrendously lengthy, and I actually wrote a VB program
to generate it.
I will also explore the customized collation alternative. I called my support group today and was told that it may just be possible for end-
users who request the option to create their own collations. After that, I'm going to take a deep breath and dive! As you mentioned earlier,
customized collations seem to be a pretty advanced feature. I may ask further questions! :)
Thank you once again for all your help!
| |
