Forum Replies Created
-
AuthorPosts
-
Ritesh
MemberVery strange.
Can you tell your MySQL server version?
Is it possible to send me a sample database and steps to reproduce the problem? We will be releasing v5.02 soon and if its a bug we will fix it in v5.02.
Ritesh
MemberIf you have a specific question then you can ask here or at: http://webyog.com/faq/addcontent.html.
We will reply to it and add it up in our FAQ database too so that another user does not have trouble finding the answer.
The help file bundled with SQLyog describes each and every option in SQLyog and it answers most of the questions of an user. Sometimes it happens that a user is looking for a question in a different way and does not find it.
Ritesh
MemberIt would be very helpful if you can tell us what is missing from the help file. We would like the help file as descriptive as possible.
I would be happy to provide you with a FREE license of SQLyog Enterprise if you are willing to work with us on this subject and help us in improving the help file.
Ritesh
MemberI can only comment that this can be done in MySQL and its pretty trivial and common. I think CalEvans will be able to help you out on this issue. His SQL is better then mine 🙂
Ritesh
MemberI mailed you the link for SQLyog Enterprise 5.02 BETA 2 that fixes this issue.
Can you confirm the fix?
Ritesh
MemberCool so it works for everybody 🙂
Ritesh
Member@samadi: I have replied to your mail with some queries.
Ritesh
Member@vygi, @peterlaursen, @carltond – You have a PM!
Ritesh
MemberThere is no restriction in the trial version. If you have selected not to use AUTHENTICATION then this error message looks strange.
Is it possible to create a temporary mail account for me at your server? You can delete the account as soon as we work on it and get the problem fixed.
Ritesh
MemberIt seems that COLUMN level comment is not supported in v3.23.x. While copying DDL from 5.x to 3.23.x, SQLyog copies the COMMENT information too and thus the process fails.
I have sent a code patch to our v5.02 development tree that will now check for TARGET MySQL version and will copy COMMENT info only if MySQL version > 4.1.
We will be releasing 5.02 BETA 2 by tomorrow evening that will have this bug fixed.
Ritesh
MemberOK, we are back in action 😀
We are now working on a similar memory related issue while importing millions of rows of data using Migration Toolkit. Once fixed, we will start working on this one.
Rest assured, 5.02 FINAL will have the bug fixed.
Ritesh
MemberWhich version of SQLyog are you using?
What is your source and target MySQL server versions?
Ritesh
MemberI think we have found the issue. Actually, there is no way in ODBC to get chunks of data as we can do in MySQL using LIMIT syntax.
So we actually do a complete SELECT * FROM TABLE, to get all the data and load them in the memory. It's not a memory leakage issue in SQLyog for sure because even Access takes up that much memory to import that same data.
The strange thing is that it works with 4.1 and not with 4.2 BETA onwards when there is no code change in the Migration Toolkit module except for support for table spaces in Oracle and Sybase.
I am looking into it and I believe we can get a solution within the next 24 hours.
Ritesh
MemberCould you please send us the CSV dump and the associated table structure? Please send it to [email protected].
We will destroy the data once we are done with the test.
Ritesh
MemberThis looks interesting.
-
AuthorPosts