You can open the 'edit sql' display. If you close it by clicking 'Cancel' or 'X' you will not get this error, you only get it when closing the dialogue by clicking 'OK'.
The idea was originally that it should be possible to edit the query. If 'OK' is used it is assumed that it was edited and we check for every column in the source.
I think we have do realize that this is not a well designed GUI here .. most users will assume that 'OK' means 'thats fine – proceed' and 'Cancel' means 'stop – I dont want this job to run. But the meaning is to approve/disapprove the changes made to the query! But I can see now that that is not very clear. Also we should make this dialogue non-editable I think!
You can open the 'edit sql' display. If you close it by clicking 'Cancel' or 'X' you will not get this error, you only get it when closing the dialogue by clicking 'OK'.
The idea was originally that it should be possible to edit the query. If 'OK' is used it is assumed that it was edited and we check for every column in the source.
I think we have do realize that this is not a well designed GUI here .. most users will assume that 'OK' means 'thats fine – proceed' and 'Cancel' means 'stop – I dont want this job to run. But the meaning is to approve/disapprove the changes made to the query! But I can see now that that is not very clear. Also we should make this dialogue non-editable I think!
Yes, it is misleading as I have already chosen the field mapping.
My impression is that by going to Edit SQL and doing nothing or any change there and then press OK, SQLyog is replacing my mapping in the background but in the GUI it shows exactly the mapping that I have done.
Maybe you should move the Edit SQL in the Table Creation section of Advanced Options and it should be activated only if I check the Drop and Recreate option.
peterlaursen
Participantbond
Memberpeterlaursen wrote on Oct 18 2007, 02:28 PM:as regards scenario #2:
