[dbusr]

The given answer is for my original question. But then I asked if it was possible to create a copy of the table without fields being dropped, not necessarily using the mentioned tools, and that one wasn’t answered. I’m assuming the answer is no but since I run into this fairly often and it is the only reason I upgraded to the Ultimate version, I want to be sure.

[dbusr]

Does the lack of a reply mean it is not possible to merge the tables?

[dbusr]

If I click the ignore altered it does skip those drops. But it also skips the alter – that of adding the missing field – so that is worse. The goal is to have the second table have the same fields as the first table. I can then run the Database Synchronization script to get the data copied over. Is there a way to accomplish this without having to manually edit the result of the Schema Synchronization script?

[dbusr]

I've sent the file to that address.

[dbusr]

The mysql version is 5.5.8. I can supply the sample but it is over a MB. I don't want to post a link since the file won't stay on the server, though I will if you want. It might be easier to email it though. If so, please let me know what address to use.

[dbusr]

Thanks for mentioning that. I checked that setting and it was set to 10 MB. I changed it to 100 MB and restarted the server. The new size shows up with the show variables command. It did make a little difference in that a little more of the file could be loaded but still fails. I copied one of the tables that has three inserts and just tried loading that and it failed. The first insert, which is where it fails is a little on 1 MB in length in a text editor. I don't know if that size is the same once mysql uses it but, if it is, this setting doesn't seem to be the reason.

[dbusr]

Thanks for the reply. I assume that when the create database, for example, is chosen from the menu, the code in SQLyog creates the command to create a database and sends it to the server. The same for the other commands. So it is would seem a simple thing to have the code issue one command and then another when the first is completed. That is not doing anything more than what it does now – just in one step. But perhaps I am missing something that prevents that from being possible.

[dbusr]

This should allow you to see the failure. This is one of the original tables

CREATE TABLE IF NOT EXISTS `products_tags` (


`products_id` int(11) NOT NULL,


`tag_id` int(10) NOT NULL


) ENGINE=MyISAM DEFAULT CHARSET=latin1;

This is the new table

CREATE TABLE IF NOT EXISTS `products_tags` (


`products_id` int(11) NOT NULL,


`tag_id` int(10) NOT NULL


) ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci;

When I run the sync tool on the above, this is what it shows as a result:

/* Alter table in target */


ALTER TABLE `products_tags` ENGINE=MyISAM, DEFAULT CHARSET='latin1' ;

[dbusr]

Ahh, OK. I didn't see that mentioned anywhere. I'm using Enterprise.

[Author]

Posts