Unsupported Screen Size: The viewport size is too small for the theme to render properly.

Forum Replies Created

Viewing 6 posts - 1 through 6 (of 6 total)
  • Author
    Posts
  • in reply to: detect changes only for specific columns #16033
    Mackenzie
    Member

    Missing a piece in my prev mail : first time my xml-sheme said : columns all=”yes”

    in reply to: detect changes only for specific columns #16032
    Mackenzie
    Member

    found the problem thanks to your xml scheme, Ritesh.

    I saved my job to an xml too to see the difference. The first time mine said :

    Want to know why? I clicked the 'next' button without 'verifying' my column-selection. I assumed my selecting would automatically be saved when i click 'next'. By clicking outside the dropdownbox (with the columns) the selection is being saved. I skipped that part and I took the saving for granted after clicking the 'next' button (windows-habit I'm afraid).

    So no need to consider this as a bug, but maybe confusing to other users as well. Anyway, I take full responsibility for my acts! Thanks again guys! 😀

    in reply to: detect changes only for specific columns #16030
    Mackenzie
    Member

    Thanks guys. Great follow-up!

    in reply to: detect changes only for specific columns #16025
    Mackenzie
    Member

    an sql script would be nice 🙂

    in reply to: detect changes only for specific columns #16024
    Mackenzie
    Member

    Thanks for your help guys. I don't know what sample data I can give from which to conclude the option settings from, but try this:

    Load the .sql script. There are 2 example db's in it : 'source' and 'target', with one identical table 'tablename1' (infact, 'target' was a copy of 'source'). The table holds one record with a primary key and 3 columns : column1 (int), column2 en column3 (both varchar). The last 2 columns have different input.

    Now this is what I did (this is SQLYog v3.71 on a win2000), I selected ONLY column1 from tablename1 (the value in both dbs for the record is 1, so the checksums should also be identical (if I understand this feature), therefore the record, the entire row should not be updated. Yet…it did…no idea why 🙁

    Table SrcRows TgtRows Inserted Updated Deleted

    ========================= ======= ======= ======== ======= =======

    `tablename1` 1 1 0 1 0

    I also tried it the other way by deselecting. Each time the record got updated in the target db. What could alter the checksums other than the numerical value of column1 ?

    in reply to: detect changes only for specific columns #16021
    Mackenzie
    Member

    I think we both are saying the same thing, but that feature didn't work for me then.

    To get it straight : w,x,y,z is data from a record:

    column | source db | target db

    1 | x | x

    2 | y | y

    3 | z | w

    I do a checksum on column 1 & 2 only (and the 'ALL' option is not selected). The record shouldn't be updated in the target db right? It did in my case when I tested it! I only downloaded a trial here yesterday, but I assume that the trial isn't any different from the registered version when it comes to this feature.

    Can you doublecheck this isn't a bug, but just me doing something wrong or still not understanding the purpose of this feature?

Viewing 6 posts - 1 through 6 (of 6 total)