collation

问题 In my SQLite 3 Database, I have some records with Turkish characters such as "Ö", "Ü", "İ" etc. When I select my values with SELECT * FROM TABLE ORDER BY COLUMN_NAME query, the records that begin with these characters are coming at the end. Normally, they should've come after the letter that is dot-less version of each. Like "Ö" is after "O", "Ü" is after "U". Is it something about regional settings? Is there a way to control these settings? I use SQLite Manager in Firefox to manage my DB.

问题 How can I see what collation a table has? I.E. I want to see: +-----------------------------+ | table | collation | |-----------------------------| | t_name | latin_general_ci | +-----------------------------+ 回答1: SHOW TABLE STATUS shows information about a table, including the collation. For example SHOW TABLE STATUS where name like 'TABLE_NAME' 回答2: The above answer is great, but it doesn't actually provide an example that saves the user from having to look up the syntax: show table status

问题 I have a problem when displaying results from a database in an HTML file in two computers. So, in one computer it shows a name like this: SAUL FRANCISCO GARCÃA RODRÃGUEZ The collation of the database is latin1_swedish_ci and the collation of the tables is utf8_general_ci . In the other computer it shows like this (I want it to be this way): SAUL FRANCISCO GARCÍA RODRÍGUEZ The names get listed in a <select> tag The language of the two browsers is English and the Html file is the same on both

问题 I have a request to change the collation of a SQL Server Database: ALTER DATABASE solarwind95 collate SQL_Latin1_General_CP1_CI_AS but I get this strange error: Meldung 5075, Ebene 16, Status 1, Zeile 1 Das 'Spalte'-Objekt 'CustomPollerAssignment.PollerID' ist von 'Datenbanksortierung' abhängig. Die Datenbanksortierung kann nicht geändert werden, wenn ein schemagebundenes Objekt von ihr abhängig ist. Entfernen Sie die Anhängigkeiten der Datenbanksortierung, und wiederholen Sie den Vorgang.

问题 My table Website Website_Name//column name Google Facebook Twitter Orkut Frype Skype Yahoo Wikipedia I i use utf8_bin collation then my query to search wikipedia in Website is Select Website_Name from Website where lower(Website_Name)='wikipedia' And if i use utf8_unicode_ci then my select query to search wikipedia in Website is Select Website_Name from Website where Website_Name='wikipedia' Now I want to know which collation is best depending upon the following queries 回答1: It depends on

问题 These two querys gives me the exact same result: select * from topics where name='Harligt'; select * from topics where name='Härligt'; How is this possible? Seems like mysql translates åäö to aao when it searches. Is there some way to turn this off? I use utf-8 encoding everywhere as far as i know. The same problem occurs both from terminal and from php. 回答1: Yes, this is standard behaviour in the non-language-specific unicode collations. 9.1.13.1. Unicode Character Sets To further illustrate

问题 By default - what is the character encoding set for a database in Microsoft SQL Server? How can I see the current character encoding in SQL Server? 回答1: If you need to know the default collation for a newly created database use: SELECT SERVERPROPERTY('Collation') This is the server collation for the SQL Server instance that you are running. 回答2: Encodings In most cases, SQL Server stores Unicode data (i.e. that which is found in the XML and N -prefixed types) in UCS-2 / UTF-16 (storage is the

问题 I have a WordPress website on my local WAMP server. But when I upload its database to live server, I get error #1273 – Unknown collation: ‘utf8mb4_unicode_520_ci’ Any help would be appreciated! 回答1: You can solve this by finding ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci; in your .sql file, and swapping it with ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE=utf8_general_ci; 回答2: I believe this error is caused because the local server and live server are running different

问题 I have an SQL query to create the database in SQLServer as given below: create database yourdb on ( name = 'yourdb_dat', filename = 'c:\program files\microsoft sql server\mssql.1\mssql\data\yourdbdat.mdf', size = 25mb, maxsize = 1500mb, filegrowth = 10mb ) log on ( name = 'yourdb_log', filename = 'c:\program files\microsoft sql server\mssql.1\mssql\data\yourdblog.ldf', size = 7mb, maxsize = 375mb, filegrowth = 10mb ) COLLATE SQL_Latin1_General_CP1_CI_AS; go It runs fine. While rest of the SQL

问题 I am using an AJAX-based lookup for names that a user searches in a text box. I am making the assumption that all names in the database will be transliterated to European alphabets (i.e. no Cyrillic, Japanese, Chinese). However, the names will still contain accented characters, such as ç, ê and even č and ć. A simple search like "Micic" will not match "Mičić" though - and the user expectation is that it will. The AJAX lookup uses regular expressions to determine a match. I have modified the