Issue was that is the query did not use `database`.`table` notation but only `table` notation, the latest USE statement got lost if SQLyog reconnected – what it frequently does with so-called 'slow servers'.
Now it will USE the database shown in the combo-box in such situation.
Hmm I wonder what has changed… I have only noticed this new behaviour lately (ie the last 1 or 2 releases..) perhaps my server has turned into a so-called 'slow server'
I have also been experiencing this. I usually have mutliple connection windows open, and when I am done with one connection, I hit the X to get to the one underneath, but it then locks, and I usually painfully lose some SQL, but such is life with BETA software.
But if there is any way I can help out in determining the problem, please let me know, it doesnt seem to pop up any debug sender or anything, just locks…
I once left it sitting there for around 10 mins, and it actually came back to life…
You know I always wondered why if you clicked the 'reply' button and not the 'quote' button, your reply would come prepopulated with the quote anyway, but have just then discovered the quote button is a toggle.
*ontopic* As stated earlier, the mapping DOES appear in the mappings list (the list of source columns and target columns and field data types etc).
Each row (an individual column mapping) has a tickbox at the start of the row.
None of these tickboxes are editable, ie, I cannot toggle them on and off. This usually doesn't bother me, as I am usually importing from access to mysql with all exact same fieldnames, and the column mapper recognises them all and ticks them *all* accordingly.
Sometimes however, it leaves a particular mapping unticked, and I cannot tick it. Upon investigation into the job xml file, it appears that the column from neither source nor target is listed at all.
*THis particular time it occured when i was using an existing import job file.*
I have just gone through the process of NOT using the existing job file, and started from scratch, using the same SQL to pull the data… selecting the same existing table
This time, as expected it mapped all the columns, and forcefully ticks every one ( i cannot untick them).
edit: forgot to mention field exists by the same name in both tables, both are numbers
Can you post little more details like how to reproduce it. Actually i am not able to find any inconsistencies
Just occured again… I think it occurs where you are using an existing job xml file, so that it sees a new column in your SOURCE SQL, and it sees the field of the exact same name in the TARGET table, it lists the match in the mappings table, however it won't let you tick it because it is not listed in the XML job file.
I have got around it by editing the XML file directly
1) The XML-did not have in it what you expected. So that is solved
2) The mapping issue. I don't understand quite if there is an issue or not?
1. Yep, solved
2. Its not an issue that I have a solid example for, More somethign that I have noticed once or twice. Will re-post once I get a solid example. Don't want to waste anyone's time.
1) The category chosen is 'Migration Tool'. Is it a Migration(ODBC-import) job we are talking about?
2) What does the… tag look like in that job file?
3) “I get this terminal error” I understand that you are running SJA from command-line?
You are PERFECTLY sure that you DID specify a job-file for MIGRATION/ODBC-import?
1.
Yes ODBC import.
2. I just took a look. It had SSH tunnel info in there, no idea why. Removed it and it starts off OK.
3. Nope running from the GUI
I love the tool, but things like being unable to tick mappings in the map popup that it automatches. Eg. It sees columns in the source and the destination tables named the same, so it matches them, they show up as a new row in the mappings table, but it wont let me TICK it. Why???
scottah wrote on May 5 2006, 05:25 AM:
1.
Yes ODBC import.
2. I just took a look. It had SSH tunnel info in there, no idea why. Removed it and it starts off OK.
3. Nope running from the GUI
I love the tool, but things like being unable to tick mappings in the map popup that it automatches. Eg. It sees columns in the source and the destination tables named the same, so it matches them, they show up as a new row in the mappings table, but it wont let me TICK it. Why???
Hmm actually in the mapping table, where it says a fieldname underneath the destination table name, doesn't mean it actually exists…. perhaps this is my problem. Although this happens to me often.. I will post more once I find a solid example.