collation

Need a case insensitive collation where ss != ß

由 主宰稳场 提交于 2019-12-12 16:07:22
问题 For a specific column in a database running on SQL Server Express 2012 I need a collation where ss and ß are not considered the same when comparing strings. Also ä and ae, ö and oe and ü and ue should be considered different respectively. Latin1_General_CI_AS provides the latter, but ss and ß are not distinguished. That is, WHERE ThatColumn = 'Fass' would yield both Fass and Faß . I would simply stick to BIN/BIN2, but I need case insensitivity. If nothing else works I'll have to use Latin1

MySQL select UTF-8 string with '=' but not with 'LIKE'

由 早过忘川 提交于 2019-12-12 14:59:03
问题 I have a table with some words that come from medieval books and have some accented letters that doesn't exists anymore in modern latin1 alphabet. I can represent these letters easily with UTF-8 combining characters. For example, to create a "J" with a tilde, I use the UTF-8 sequence \u004A+\u0303 and the J becomes accented with a tilde. The table uses utf8 encoding and the field collation is utf8_unicode_ci. My problem is the following: If I try to select the entire string, I receive the

SQL Server: impact of column collation on T-SQL instructions

由 爷，独闯天下 提交于 2019-12-12 14:18:17
问题 I discovered(*) today that, depending on the server, my TSQL commands were case-sensitive, meaning that, when one table's column is named tableId , the following instruction might not succeed: SELECT TableId FROM myTable Depending on the column's collation. SQL_Latin1_blablabla seems not to be case-sensitive, when Latin1_blablabla is. So my first question is WHY!!! And the second one is: what is the quickest trick (sp?) to change all collations for all concerned columns in the database? EDIT:

Getting error Illegal mix of collations (utf8mb4_unicode_ci,IMPLICIT) and (utf8mb4_general_ci,IMPLICIT) for operation '='

由 a 夏天 提交于 2019-12-12 14:08:46
问题 I am getting the error below when trying to do a select through a stored procedure in MySQL Illegal mix of collations (utf8mb4_unicode_ci,IMPLICIT) and (utf8mb4_general_ci,IMPLICIT) for operation '='. SHOW VARIABLES WHERE Variable_name LIKE 'character\_set\_%' or Variable_name LIKE 'collation%'; 'character_set_client', 'utf8' 'character_set_connection', 'utf8' 'character_set_database', 'utf8mb4' 'character_set_filesystem', 'binary' 'character_set_results', 'utf8' 'character_set_server',

SQLite case sensitive search with collate nocase field

由 人盡茶涼 提交于 2019-12-12 11:43:07
问题 I have a database (which I cant change) that has a collate nocase field: name string collate nocase I need to do a search on this field that is case sensitive. Is this possible with the 'collate nocase'? Thanks 回答1: Just switch the collation back for that query: SELECT * FROM MyTable WHERE name COLLATE BINARY = 'Nick' 来源： https://stackoverflow.com/questions/14947945/sqlite-case-sensitive-search-with-collate-nocase-field

Latin characters in phpMyAdmin with UTF-8 collation

由 陌路散爱 提交于 2019-12-12 09:43:20
问题 My website uses: <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml"> And this meta: <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> I created my database and tables in phpMyAdmin making sure everything is set as utf8_unicode_ci (table, fields, database), even the connection collation. When I insert some latin characters (accents, ñ and stuff like that) into

Cyrillic symbols in SQL code are not correctly after insert

由 我怕爱的太早我们不能终老 提交于 2019-12-12 08:52:14
问题 I use SQL Server 2005 and I am try to store Cyrillic characters but I can't with SQL code by trying to run this is SQL Server: INSERT INTO Assembly VALUES('Македонски парлиамент број 1','',''); Or from C# is happening the same problem but inserting/updating the column from SQL Server it work and it is store normally. The datatype of column is nvarchar . 回答1: You have to add N prefix before your string. When you implicitly declare a string variable it is treated as varchar by default. Adding

Execute sqlite3 “dot” commands from Python or register collation in command line utility

由 旧街凉风 提交于 2019-12-12 08:18:35
问题 My sqlite3 database contains a "collate" column-constraint. I've placed it in the schema for the table, to prevent accidentally neglecting to use the necessary collation. However this means when running sqlite3 from the command line, and not from my Python code, the collation referenced in the schema is not present, and I'm unable to use dot commands. sqlite> .import data.txt table_name Error: no such collation sequence: my_collation Furthermore, creating the connection from Python, and

SQL Query + special characters ä, ö, ü, ø etc

由 血红的双手。 提交于 2019-12-12 06:01:54
问题 I'm wrapping my head around a problem for the last couple of days and need some tips on how to solve the problem. I have a sql query which looks like this mysql_real_escape_string($value); $sql_first = "SELECT `user_id` FROM `usermeta` WHERE `meta_value` = '".$value."' It works fine if $value isn't containing characters like ä ü ö ø The collation of the database is utf8_general_ci I tried various combinations with the php conv() function, but can't get it to work. I guess I have to convert

DB collation and chartset setting in Mysql (in Laravel)

由 怎甘沉沦 提交于 2019-12-12 04:46:11
问题 I am using external DB(charset:latin1_swedish_ci, collation=latin1, MyISAM) with internal DB(utf8mb4_unicode_ci, utf8mb4, InnoDB). customer_name : collation = utf8mb4_unicode_ci customer_email : collation = utf8mb4_unicode_ci So everytime I get the below exception warning when getting data from external DB. How should I modify DB setting in my situation? Thanks. (3/3) QueryException SQLSTATE[HY000]: General error: 1366 Incorrect string value: '\xF8peri ...' for column 'customer_name' at row 1
订阅 collation