Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
Halil416
Starting Member
5 Posts |
 Posted - 2007-01-28 : 16:08:23
|
| hi everyone,I have a problem related with character sets and unicodingI have a multi-language db and I am using sql to retrieve data from it.In Turkish language UPPER case for 'i' is 'Ý', while as you know in english Upper case for 'i' -> 'I' instead..Also UPPER case for 'ý' is 'I' in turkish.I have thousands of turkish and english words combined in rows.Now what I am trying to do is to build a search mechanism.SELECT column_a LIKE %iiii%type of search returns casesensitive result, which i would not prefer..What I want is any combinations iniIiIÝiIiiiiI.......as a result from query as the one above...(consider that this list can be lengthened as the number of chars increases.)So first question is:1.) is there a way to allow above statement act as it is supposed to?NOT being exact solution but being a part of it, enforcing LIKE to beNOCASE-SENSITIVE might narrow down the number of combinations soI would write a function to handle the rest of combinations possible and that will handle the stuation.2.)is it possible to make LIKE command to allow NOCASE-SENSITIVE data?I am using DELPHI7 + PARADOX + BDEQUERY OBJECT |
|
|
nr
SQLTeam MVY
12543 Posts |
Posted - 2007-01-28 : 23:01:05
|
| tryx like 'xxx' collate xxxxxxxTo get a list of available collationsselect * from fn_helpcollations()==========================================Cursors are useful if you don't know sql.DTS can be used in a similar way.Beer is not cold and it isn't fizzy. |
 |
|
|
Kristen
Test
22859 Posts |
|
|
|
|
|
LIKE to be NOCASE-SENSITIVE