Foreign key names also have to be unique, so just give a different name to the. I also worked with Workbench, and in local worked perfectly, also worked good in production, until I recreate schema on production server with Forward Engineering. ![]() ![]() Changing the type of the original field doesnt change the type of the. One of possible cause could be default storage engine on production db. ![]() com / youtube / vitess / examples / local $ vtctlclient - server localhost : 15999 applyschema - sql "drop table items " test_keyspaceĮ0112 03 : 38 : 32.332120 3782 main. I cannot create a table using the following: The table Users already exists in the DB, only UserTimeZones is to be added, and it fails. In the hoteltask table you have already defined a foreign key named roomid. From what Ive read about MySQL constraints this is caused by the different field types.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |