mainframe

Thank you Larry for your help. Your solution worked perfectly in the interim! After changing the storage engine to MyISAM and attempting other workarounds, the problem still incurred. Later I realised for a specified key to be too long, the charset used in the client must be consuming too many bytes and could therefore not be UTF8. The problem was due to my accidental omission of: CHARSET UTF8; I would have expected unusual characters to be stored in the database if the charset were wrong however this was an error thrown before any database population could have taken place. Cheers and thanks again, MF

Hello, I would appreciate any assistance I can receive. While following the instructions provided in chapter 17 to create the users table for the forum2 database (page 553), I had encountered the following error: CREATE TABLE users ( -> user_id MEDIUMINT UNSIGNED NOT NULL AUTO_INCREMENT, -> lang_id TINYINT UNSIGNED NOT NULL, -> time_zone VARCHAR(30) NOT NULL, -> username VARCHAR(30) NOT NULL, -> pass VARCHAR(255) NOT NULL, -> email VARCHAR(60) NOT NULL, -> PRIMARY KEY (user_id), -> UNIQUE (username), -> UNIQUE (email), -> INDEX login (username, pass) -> ); Error message: #1071 - Specified key was too long; max key length is 1000 bytes Some additional information: Currently using paid hosting. My database character set is: utf8mb4 My database collation is: utf8mb4_unicode_ci All tables use: InnoDB. I would like to please know how this error can be resolved to continue proceeding with the chapter. Enjoying the book! Many thanks, MF.