Forum Replies Created
-
AuthorPosts
-
RiteshMember
Thanks.
I have added it in the TO-DO list of SQLyog.
RiteshMemberQuote:sync structureWe always supported Structure Sync without PRIMARY KEYS.
RiteshMemberIts not out yet. It will take another 3-4 days 🙂
RiteshMemberQUOTE(stroperyliad @ May 21 2004, 04:13 PM)Found the solution: this error only occures only with sja2.0 😡 , the old version sja1.1 works perfect 😀[snapback]3030[/snapback]This is due to the fact that sjasession.xml implementation was done in v2.0 and thus its failing!
RiteshMemberSJA takes two parameters as suggested in the docs:
CODEsja jobfile -llogfileNote: there is no space between -l and the logfile. If you dont specify -l, then SJA will create sja.log in the same folder from where SJA is executed.
Other then sja.log, SJA also creates sjasession.xml which has error written in XML format. You cannot specify the path for this file and it will always open up in the same folder as SJA. This basically requires that the path of SJA has write permission otherwise SJA wont be able to create the sjasession.xml and hence it will stop after throwing up the error:
Error opening session ERROR log file.
We acknowledge that this is a bad design and we plan to fix it in 4.2 BETA 4. v4.2 BETA 3 will be released today and we dont want to change the code so late in the release. You can expect BETA 4 anytime next week 🙂
RiteshMemberWe will reimplement it in v4.2 BETA 3. v4.2 BETA 3 is couple of days away 🙂
RiteshMemberWhat is the error you are getting?
Can you give me more info about your MySQL (source and target) & SQLyog versions? How big is the table that you are trying to sync?
RiteshMemberHost address is nothing much but the computer address in which your MySQL server is running.
Can you give us more details about your setup?
RiteshMemberAll's well that end's well 🙂
RiteshMemberRiteshMemberThis is very strange.
Can you mail me sample data to reproduce the error at our end?
RiteshMemberAs you know, we plan to completely overhaul the language issues in v4.3. This proposal is already in the plan for v4.3 where a user can actually specify the collation to be used.
With v4.3, issues similar to PvUtrix's will be fixed 🙂
RiteshMemberWhich version of SQLyog are you using?
RiteshMemberI am not sure if I understood the problem. Can you post a screenshot?
RiteshMemberSorry for the delay in replying. We are still working on BETA 3 (there are number of bugs that are still to be fixed).
Though the Error 1064 bug can fixed by applying the following patch in SQLyogTunnel.php.
Change:
Code:Â Â /* fix in v4.1 that checks for global configuration flag get_magic_quotes_gpc() to stripslashes or not */
  if (get_magic_quotes_gpc()) {
    $xmlrecvd = stripslashes ( urldecode ( $_POST['textfield'] ) );
  } else {
    $xmlrecvd = urldecode ( $_POST['textfield'] );
  }  Âto
Code:Â Â /* fix in v4.1 that checks for global configuration flag get_magic_quotes_gpc() to stripslashes or not */
  if (get_magic_quotes_gpc()) {
    $xmlrecvd = stripslashes ( rawurldecode ( $_POST['textfield'] ) );
  } else {
    $xmlrecvd = rawurldecode ( $_POST['textfield'] );
  }   -
AuthorPosts