Billy Posted August 31, 2021 Posted August 31, 2021 1) What's the proper "Collation" when creating a database? latin1_swedish_ci just doesn't seem right. 2) If I have databases in latin1_swedish_ci what's the best recourse to fix them? TIA
datakick Posted August 31, 2021 Posted August 31, 2021 CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci ALTER TABLE <table> CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci; 1
Billy Posted August 31, 2021 Author Posted August 31, 2021 (edited) 5 hours ago, datakick said: CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci ALTER TABLE <table> CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci; Thank you DK! Here is a snap of my live server... ? Strange Edited August 31, 2021 by Script-Fu removed my snap
Billy Posted August 31, 2021 Author Posted August 31, 2021 (edited) Here are two snaps of live websites. One is presta v1.6.1.10 and the other is thirty bees v1.2.0 Edited August 31, 2021 by Script-Fu same
Billy Posted August 31, 2021 Author Posted August 31, 2021 (edited) Last snap to clarify I have a lot of stuff messed up! This is from my localhost aka wamp64server phpmyadmin Now I need to figure out how to make my localhost wamp64 default to the same settings I have on my live vps server. So this doesn't happen NO more. Sheesh... No wonder nothing is going my way atm. Never get old or for that matter trust a fart! Edited August 31, 2021 by Script-Fu same
Billy Posted August 31, 2021 Author Posted August 31, 2021 (edited) @datakick Pretty sure I don't fully understand your generous reply above. Can you elaborate a little more? Edited August 31, 2021 by Script-Fu same
yaniv14 Posted August 31, 2021 Posted August 31, 2021 <table> should be replaced by any table you wish to modify. e.g. "ps_cart" to change on database run: ALTER DATABASE <db name> CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci; when <db name> is you db name 1
the.rampage.rado Posted August 31, 2021 Posted August 31, 2021 13 minutes ago, yaniv14 said: <table> should be replaced by any table you wish to modify. e.g. "ps_cart" to change on database run: ALTER DATABASE <db name> CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci; when <db name> is you db name If he/she doesn't know basic sql sintax and does not know what should be replaced it's better to leave it as it is. I doubt there will be any issues.
Billy Posted August 31, 2021 Author Posted August 31, 2021 43 minutes ago, yaniv14 said: <table> should be replaced by any table you wish to modify. e.g. "ps_cart" to change on database run: ALTER DATABASE <db name> CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci; when <db name> is you db name Thank you @yaniv14
Billy Posted August 31, 2021 Author Posted August 31, 2021 31 minutes ago, the.rampage.rado said: If he/she doesn't know basic sql sintax and does not know what should be replaced it's better to leave it as it is. I doubt there will be any issues. haha one day you will be old too just saying
musicmaster Posted August 31, 2021 Posted August 31, 2021 Don't worry. You don't have any character set/collation problem. utf8mb4 is just preferred for Thirty Bees. There is no obligation. Anyone who has migrated from Prestashop has an utf8 variant. Prestashop only switched to utf8mb4 with 1.7.6 or 1.7.7. That latin_swedish collation isn't a problem either. Some modules that have their own tables make them in the format that they prefer. And that is ok. 1
datakick Posted September 1, 2021 Posted September 1, 2021 15 hours ago, musicmaster said: That latin_swedish collation isn't a problem either. It can be a problem if you are using language with non ascii characters, such as ěščřžýáí. Search, ordering and comparison would not work as expected.
datakick Posted October 8, 2021 Posted October 8, 2021 36 minutes ago, meshare said: utf8mb4 is just preferred for Thirty Bees. There is no obligation. Anyone who has migrated from Prestashop has an utf8 variant. shareit Vidmate APK utf8 encoding is basically utf8mb3, and as such it can't store some utf8 characters. While most merchants will not encounter any issues with this, it's still recommended to update to utf8mb4 to be sure no data will be lost when saved to database. Most importantly, without utf8mb4 encoding, you can't enter emojis into your product descriptions. And we can't allow that. /s
wakabayashi Posted October 8, 2021 Posted October 8, 2021 48 minutes ago, datakick said: Most importantly, without utf8mb4 encoding, you can't enter emojis into your product descriptions. And we can't allow that. /s I fully agree and like the change! It's quite important these days. Every field that has customer interaction might see emojis. If you like it or not, doesn't matter, customer do use it. I could also imagine that some merchant's want to use it their own. ☺️
Briljander Posted October 10, 2021 Posted October 10, 2021 Is it safe to update to utf8mb4_unicode_ci from utf8mb4 or can there be any loss of data or something?
selenamorriss Posted October 12, 2021 Posted October 12, 2021 hello everyone.. i've recently joined this website. :)
the.rampage.rado Posted October 13, 2021 Posted October 13, 2021 Good to know, On 10/12/2021 at 4:42 PM, selenamorriss said: hello everyone.. i've recently joined this website. :) Now pass us the aff links and never log back in! 😄 1
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now