How can we help you today? How can we help you today?
neil.anderson
Ah I see. The installer itself needs space to unpack before installing Data Compare. You can set this to your other drive by setting an environment variable called RGTEMP to point to the required location. / comments
Ah I see. The installer itself needs space to unpack before installing Data Compare. You can set this to your other drive by setting an environment variable called RGTEMP to point to the required l...
0 votes
Hi awestrope, I believe this to be fixed in the latest version. Please download it from http://mysql-compare.com/download . If you still have the same problem with the latest version please let me know. Thanks, Neil / comments
Hi awestrope, I believe this to be fixed in the latest version. Please download it from http://mysql-compare.com/download . If you still have the same problem with the latest version please let me ...
0 votes
Hi Martijn, Thanks for reporting this to us. You are not doing something stupid, it is a bug in the EAP. We will fix it asap and have a new build for you soon. Regards, Neil / comments
Hi Martijn, Thanks for reporting this to us. You are not doing something stupid, it is a bug in the EAP. We will fix it asap and have a new build for you soon. Regards, Neil
0 votes
Hi rspooner, thanks for trying out Schema Compare for Oracle. Is there an option where the schema name (and any associated double quotes on the schema name and the object name) can be ignored if the schema name matches the name of the schema you entered in the Source/Target dialog? I am using Schema Compare to compare the contents of a number of schemas, one at a time, against a "master" schema. Some of our PL/SQL contains schema names. When I compare a SOURCE schema against a TARGET schema, Schema Compare flags such lines as differences, which is not what I was hoping for. As an example, I have: In SOURCE: Code: CREATE TRIGGER "SOURCE".TRIGGER1 AFTER DELETE.... In TARGET: Code: CREATE TRIGGER "TARGET".TRIGGER1 AFTER DELETE.... While I accept these two lines are lexically different, each schema would react identically when the PL/SQL is executed in each schema, and I don't want Schema Compare to flag such differences. There are probably over 3,000 such lines flagged by Schema Compare per comparison in my environment, which is rather a lot to go through and eyeball! My understanding is that Schema Compare already does this by default at the moment. PL/SQL that differs just by the schema name is not considered different and appears as an identical object, but if you select it, the SQL Differences pane will still highlight any textual differences in the creation script. If you are seeing objects which are flagged as different and the only difference appears to be the schema name then it would be useful if you could provide us with further information so we can investigate. Developing this a stage further: If there was another schema name specified which did not match the schema under scrutiny: In SOURCE: Code: CREATE TRIGGER "SOURCE".TRIGGER2 AFTER DELETE.... In TARGET: Code: CREATE TRIGGER "MASTER".TRIGGER2 AFTER DELETE.... I would want this flagged as a difference. Also: If there a schema name was missing, but the schema name which was present matched the name of the schema under scrutiny, perhaps there should be a "sub-option" to determine whether or not a difference should be flagged: In SOURCE: Code: CREATE TRIGGER "SOURCE".TRIGGER3 AFTER DELETE.... In TARGET: Code: CREATE TRIGGER TRIGGER3 AFTER DELETE.... But the following is definitely a difference, as you are specifying a schema name on the object which is not the same as the schema under scrutiny. In SOURCE: Code: CREATE TRIGGER "MASTER".TRIGGER3 AFTER DELETE.... In TARGET: Code: CREATE TRIGGER TRIGGER3 AFTER DELETE.... Thanks for your suggestions. We will consider this as a feature request for future releases of the tool. Regards, Neil Anderson / comments
Hi rspooner, thanks for trying out Schema Compare for Oracle. Is there an option where the schema name (and any associated double quotes on the schema name and the object name) can be ignored if t...
0 votes
Hi guys, I know this has been a long time coming, but this bug (along with several others) is fixed!. You can download the latest version of both tools from www.mysql-compare.com. Regards, Neil / comments
Hi guys, I know this has been a long time coming, but this bug (along with several others) is fixed!. You can download the latest version of both tools from www.mysql-compare.com. Regards, Neil
0 votes