Re: Eine Tabelle soll nur angelegt werden wenn diese nicht existiert

[Jon Stephens]

Hallo,


Fûr mich funktioniert der Satz wieso:

mysql> create table if not exists tb1 ( Kunden_id nvarchar(50), Vorname nvarchar(50), Nachname nvarchar(50), Email nvarchar(50) );
Query OK, 0 rows affected, 4 warnings (0.02 sec)

mysql> SHOW WARNINGS\G
*************************** 1. row ***************************
  Level: Warning
   Code: 3720
Message: NATIONAL/NCHAR/NVARCHAR implies the character set UTF8MB3, which will be replaced by UTF8MB4 in a future release. Please consider using CHAR(x) CHARACTER SET UTF8MB4 in order to be unambiguous.
*************************** 2. row ***************************
  Level: Warning
   Code: 3720
Message: NATIONAL/NCHAR/NVARCHAR implies the character set UTF8MB3, which will be replaced by UTF8MB4 in a future release. Please consider using CHAR(x) CHARACTER SET UTF8MB4 in order to be unambiguous.
*************************** 3. row ***************************
  Level: Warning
   Code: 3720
Message: NATIONAL/NCHAR/NVARCHAR implies the character set UTF8MB3, which will be replaced by UTF8MB4 in a future release. Please consider using CHAR(x) CHARACTER SET UTF8MB4 in order to be unambiguous.
*************************** 4. row ***************************
  Level: Warning
   Code: 3720
Message: NATIONAL/NCHAR/NVARCHAR implies the character set UTF8MB3, which will be replaced by UTF8MB4 in a future release. Please consider using CHAR(x) CHARACTER SET UTF8MB4 in order to be unambiguous.
4 rows in set (0.00 sec)

Gemäß diese angezeigten Warnungen soll man stattdessen CHAR(x) CHARACTER SET UTF8MB4 (oder VARCHAR(x) CHARACTER SET UTF8MB4) verwenden. (Nicht UTFMB3 wenn möglich, da dieser Zeichensatz später weggehen wird.)

cheers,

Jon Stephens
MySQL Documentation Team @ Oracle

MySQL Dev Zone
MySQL Server Documentation
Oracle