Ryan on Office Interop DCOM Config on a Windows Server IIS Machine to open Word, Excel and Access files with ASP.NET C#.Priya Sinha on Things to consider when hiring Angular Developers.Like operator for integer on LIKE operator equivalent for integer / numeric value Columns in a SQL (or T-SQL) Database.Suren S M on AsyncUtil - C# Helper class to run async methods as sync and vice-versa. ![]() When this happens, we can convert one or more Databases and/or all their Tables and/or all their table Columns into a specific Collation using the following sets of commands. However, there are some scenarios - for example when switching from MyISAM default to InnoDB default, or when moving a DB between different servers with different settings - where you need to normalize the Collation among multiple tables belonging to one (or more) Database(s). Illegal mix of collations (utf8_general_ci,IMPLICIT) and (utf8_unicode_ci,IMPLICIT) for operation When working with MySQL database it's a good practice to use the same Collation on tables which we need to JOIN or UNION during FULL-TEXT and/or LIKE based searches, to avoid errors such as the following: A collation is a set of rules for comparing characters in a character set. ![]() In case you don't know what the term Collation actually stands for, you can get the proper definition from the official MySQL docs:Ī character set is a set of symbols and encodings. That same approach can be used if we need to convert all the tables to a specific Collation. A few months ago I wrote an article explaining how to convert all MySQL tables belonging to one or more Database(s) from MyISAM to InnoDB and vice-versa with a simple, yet effective CONCAT-based query.
0 Comments
Leave a Reply. |