collation

问题 I was creating this SQL function from SQL SERVER 2008 R2 to WINDOWS AZURE, but I don't how to resolve this problem. Msg 468, Level 16, State 9, Procedure GetObjectivesByTest, Line 69 Cannot resolve the collation conflict between "SQL_Latin1_General_CP1_CI_AS" and "Modern_Spanish_CI_AS" in the equal to operation. CREATE FUNCTION [dbo].[GetObjectivesByTest](@testId smallint) RETURNS @res TABLE ( -- Add the column definitions for the TABLE variable here ObjectiveId smallint NOT NULL, Name

问题 I am converting a Delphi program from the BDE to Advantage Database. On weekends I work on a Win 7 machine using Delphi XE. During the week I work on a Win XP machine using Delphi 7. Advantage tables work fine on the Win 7 machine but when copied to the XP machine they cannot be accessed - Error 5175 the index was created with a different collation sequence I have searched the net, even gone into the Advantage forums but can't find anything helpful. The XP and Win 7 are both set up the same

问题 We have issues with utf8-string comparisons in MySQL 5, regarding case and accents : from what I gathered, what MySQL implements collations by considering that "groups of characters should be considered equal". For example, in the utf8_unicode_ci collation, all the letters "EÉÈÊeéèê" are in the same box (together with other variants of "e"). So if you have a table containing ["video", "vidéo", "vidÉo", "vidÊo", "vidêo", "vidÈo", "vidèo", "vidEo"] (in a varchar column declared with ut8_general

问题 We have issues with utf8-string comparisons in MySQL 5, regarding case and accents : from what I gathered, what MySQL implements collations by considering that "groups of characters should be considered equal". For example, in the utf8_unicode_ci collation, all the letters "EÉÈÊeéèê" are in the same box (together with other variants of "e"). So if you have a table containing ["video", "vidéo", "vidÉo", "vidÊo", "vidêo", "vidÈo", "vidèo", "vidEo"] (in a varchar column declared with ut8_general

问题 I am using SQL Server 2008 express edition and its collation settings are set to default.I wish to store special characeters like á ,â ,ã ,å ,ā ,ă ,ą ,ǻ in my database but it converts them into normal characters like 'a'. How can I stop SQL Server from doing so? 回答1: Make sure that your columns are using the type nvarchar(...), rather than varchar(...). The former is Unicode, the latter is ASCII. Also, make sure that your database default collation is set to Accent Sensitive, and that your

问题 I have a table with text field. I want to select rows where text is in all caps. This code works as it should, and returns ABC : SELECT txt FROM (SELECT 'ABC' AS txt UNION SELECT 'cdf') t WHERE txt COLLATE SQL_Latin1_General_CP1_CS_AS = UPPER(txt) then I create UDF (as suggested here): CREATE FUNCTION [dbo].[fnsConvert] ( @p NVARCHAR(2000) , @c NVARCHAR(2000) ) RETURNS NVARCHAR(2000) AS BEGIN IF ( @c = 'SQL_Latin1_General_CP1_CS_AS' ) SET @p = @p COLLATE SQL_Latin1_General_CP1_CS_AS RETURN @p

问题 My Table collation is "utf8_general_ci". If i run a query like: SELECT * FROM mytable WHERE myfield = "FÖÖ" i get results where: ... myfield = "FÖÖ" ... myfield = "FOO" is this the default for "utf8_general_ci"? What collation should i use to only get records where myfield = "FÖÖ"? 回答1: SELECT * FROM table WHERE some_field LIKE ('%ö%' COLLATE utf8_bin) 回答2: A list of the collations offered by MySQL for Unicode character sets can be found here: http://dev.mysql.com/doc/refman/5.0/en/charset

问题 My Table collation is "utf8_general_ci". If i run a query like: SELECT * FROM mytable WHERE myfield = "FÖÖ" i get results where: ... myfield = "FÖÖ" ... myfield = "FOO" is this the default for "utf8_general_ci"? What collation should i use to only get records where myfield = "FÖÖ"? 回答1: SELECT * FROM table WHERE some_field LIKE ('%ö%' COLLATE utf8_bin) 回答2: A list of the collations offered by MySQL for Unicode character sets can be found here: http://dev.mysql.com/doc/refman/5.0/en/charset

问题 How do you setup a SQL Server 2005 DBMS, so that you can store data in different languages? My exact problem is this: in SQL Server Management Studio I'm writing an insert statement which contains German Umlauts. Text is successfully saved but reading the same value results in text without Umlaut. Consider that I have to support 4 languages: English, German, Greek & Russian (I don't want to think what I will face with the Russian text). The DBMS is now setup with Greek collation (to support

问题 I have a list of words in Arabic that I'd like to sort. I have tried the standard Collator with different Locales (like English or French but without much hope) and I have even created my own RuleBasedCollator but to no avail. Apparently the default sorting relies on the unicode values order, which in many cases works but apparently not in this one. Following the instructions of the javadocs, the RuleBasedCollator requires a string specifying the characters in the order you want them sorted.