Used by
MySQL 5.7 - x64
Open Server - the last
heidisql

MySQL is located
e: \ srw \ MySQL-5.7-x64

Databases are located in the local network
\ Server \ e \ srv \ db \ webopsrvr \ userdata \ MySQL-5.7-x64 \

DESCRIPTION
The table name is 002_tst_01_vr_05_tbl_frm1_ssl

-- Works !!!

CREATE TABLE tst_rb_mn_03.002_tst_01_vr_05_tbl_frm1_ssl (id_tma_ssl INT, name_ssl TEXT, url_ssl TEXT );

-- DOES NOT WORK

 CREATE TABLE IF NOT EXISTS `002_tst_01_vr_05_tbl_frm2_ssl` ( `id_tma_ssl` INT(11) DEFAULT NULL, `name_ssl` text, `url_ssl` text ) ENGINE=InnoDB DEFAULT CHARSET=utf8;

When you run this command, an error appears:
SQL Error (1050): Table ' tst_rb_mn_03 . 002_tst_01_vr_05_tbl_frm2_ssl 'already exists see screen.

 INSERT INTO `002_tst_01_vr_05_tbl_frm2_ssl` (`id_tma_ssl`, `name_ssl`, `url_ssl`) VALUES (4, 'name_ssl_05_tbl_zp_1 ', 'url_ssl_05_tbl_zp_1 '), (5, 'name_ssl_05_tbl_zp_2 ', 'url_ssl_05_tbl_zp_2 '), (6, 'name_ssl_05_tbl_zp_3 ', 'url_ssl_05_tbl_zp_3 ');

Table name - tst_01_vr_05_tbl_frm1_ssl - Works

 CREATE TABLE IF NOT EXISTS `tst_01_vr_05_tbl_frm2_ssl` ( `id_tma_ssl` INT(11) DEFAULT NULL, `name_ssl` text, `url_ssl` text ) ENGINE=InnoDB DEFAULT CHARSET=utf8; INSERT INTO `tst_01_vr_05_tbl_frm2_ssl` (`id_tma_ssl`, `name_ssl`, `url_ssl`) VALUES (4, 'name_ssl_05_tbl_zp_1 ', 'url_ssl_05_tbl_zp_1 '), (5, 'name_ssl_05_tbl_zp_2 ', 'url_ssl_05_tbl_zp_2 '), (6, 'name_ssl_05_tbl_zp_3 ', 'url_ssl_05_tbl_zp_3 ');

Question.
Why aren't tables created with names starting with numbers?

enter image description here

  • if not exists .. - vp_arth
  • [offtop] This is not your first question here on problems the source of which is your own errors when migrating the MySQL server data directory. Maybe enough to deal with the consequences? eliminate, finally, the cause of the problems. [/ offtop] - Akina
  • @Akina I do not understand you ... You mean that the problems are due to the fact that the data directory is on another computer? - koverflow
  • one
    I mean that there is a serious mistake, as a result of which various negative effects are observed. The source of this error is incorrect transfer of the database location directories. What exactly is the mistake - I have no idea. And yes - the fact that the database directory is located on another host may well be part of the error. It may not be. - Akina
  • @Akina Damn ... it’s strange that some tables with a creak were imported ... prntscr.com/efzjo6 ... Okay ... I'll think about something .. - koverflow

0