Data Compare: Where clause editor bug

• 
  Thanks for that I'll look into it. Hope apart from that you like the filter feature as it should enable people with very large tables that change only via appends to compare a lot quicker.
  
  Have you had a look at the compare using checksum feature in the options? That makes tables that infrequently change compare in a fixed time regardless of the size of the table.

  richardjm March 06, 2006 03:02

  - 0 +
• 
  The where clause on a table is great as we have tables that have system types and client specific type data in them, the where clause allows me to only synchronise the appropriate rows.
  
  Would it be possible to specify a columns value based on a sql statement eg
  the primary key on a table is an int(not seeded) when adding rows to the target table the primary key needs to be max +1, as the Primary keys are not seeded and do not match up between different roots, I exclude this column in the comparison, unfortunately the Insert fails as the Primary key is Null if I could specify the field as sql statement the insert would not fail.
  
  I have not used the checksum feature yet, I will have a play later on
  
  Andy

  AndyScott March 06, 2006 09:47

  - 0 +
• 
  I suppose you could do something like introduce a trigger for inserting into the table at the beginning of the script and at the end of the migration script you could remove the trigger so it wouldn't effect the normal operation of the table. We've not plans to introduce a feature allowing you to edit a "template" of the insert script for want of a better term at present.

  richardjm March 06, 2006 09:57

  - 0 +
• 
  Thanks for the response, I will carry on playing around with the primary key problem until I find a suitable solution

  AndyScott March 06, 2006 10:01

  - 0 +

Add comment

Please sign in to leave a comment.