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

Forum Replies Created

Viewing 15 posts - 631 through 645 (of 2,527 total)
  • Author
    Posts
  • in reply to: 4.2 Beta2 Sync Bug? Or No Support Yet? #19283
    Ritesh
    Member

    Sorry 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'] );
       }    
    in reply to: Sqlyog Enterprise And Paypal #19286
    Ritesh
    Member
    in reply to: Delimiter In Sqlyog #19285
    Ritesh
    Member
    Quote:
    No blank character (or a line-break) is allowed between new and old DELIMITER. Is that a necessary restriction? If yes, the FAQ should be adjusted accordingly!

    Currently yes. I will fix this issue in BETA 3 or 4.

    Quote:
    Is it absolutley necessary to use DELIMITER //; when script is running from a file

    Yes.

    I have added this issue in TO-DO list. We will fix it by 4.2 FINAL.

    Quote:
    I'd prefer that “import from SQLdump” was changed to “exetute file with sql-statements” because the SQL does not need to be a dump. It can be any SQL.

    I will discuss it with my fellow people and do accordingly 🙂

    in reply to: Syntax Bug #19284
    Ritesh
    Member

    Will be fixed in BETA 3.

    We are able to create SPs with that syntax itself 😀

    in reply to: Feature Request #19269
    Ritesh
    Member

    I have added your request in the TO-DO list. Though I cannot guarantee you which version of SQLyog will have this feature.

    in reply to: Multiple Queries For Odbc Import #19280
    Ritesh
    Member

    Yes, you are correct. You can import data from two results in one job session. You will need to have two job sessions.

    I have written this in the TO-DO list of SQLyog but I cannot guarantee which version will have this feature.

    in reply to: Migration Toolkit #19281
    Ritesh
    Member

    Can you mail me the job file?

    in reply to: 4.2 Beta2 Sync Bug? Or No Support Yet? #19282
    Ritesh
    Member
    sdozono wrote on Sep 24 2005, 12:30 AM:
    (Still, I need to add 'SET NAMES UJIS' in my SQLyogtunnel.php…  😎 )

    Error messages appeared during sync tests of tables that has combined index keys…

    Message:

    SQLYOG Wizard: “There was an error while execute a query. The query and the error has been logged in the log file.

    Check D:Program FilesSQLyog Enterprisesja.log for complete error details.

    SJALOG:

    Error No. 1064

    You have an error in your SQL syntax. Check the manual that corresponds to your MySQL server version for the right syntax to use near '0)) as `CAL_DATE`, max(char_length(abs(`PLAN_ID`))) as `PLAN_ID

    Error SQL syntax. (Source Server:)

    select max(char_length(`CAL_DATE` 0)) as `CAL_DATE`, max(char_length(abs(`PLAN_ID`))) as `PLAN_ID` from `calendar`

    CREATE TABLE `calendar` (

    `CAL_DATE` date NOT NULL default '0000-00-00',

    `PLAN_ID` int(11) NOT NULL default '0',

    `******` tinyint(4) default NULL,

    `******` tinyint(4) default NULL,

    `******` tinyint(4) default NULL,

    `******` tinyint(4) default NULL,

    `******` time default NULL,

    `******` time default NULL,

    PRIMARY KEY (`CAL_DATE`,`PLAN_ID`)

    ) ENGINE=MyISAM DEFAULT CHARSET=ujis;

    A character '0' is the problem..

    [post=”7299″]<{POST_SNAPBACK}>[/post]

    This is the same bug as:

    http://www.webyog.com/forums/index.php?showtopic=1694

    We will be releasing BETA 3 today that has the bug fix.

    Your second request has also been implemented in BETA 3 🙂

    in reply to: Erro No 1064 – When Syncing #19276
    Ritesh
    Member
    pete wrote on Sep 23 2005, 02:46 PM:
    Excellent!

    Thanks for the help!

    You guys rock!

    [post=”7291″]<{POST_SNAPBACK}>[/post]

    😛 😛

    in reply to: Erro No 1064 – When Syncing #19274
    Ritesh
    Member

    Bug fixed in 4.2 development tree 🙂

    in reply to: Erro No 1064 – When Syncing #19273
    Ritesh
    Member

    Thanks for the sample data.

    We are able to reproduce the error. We will be releasing 4.2 BETA 3 tomorrow that will have the bug fix.

    in reply to: Erro No 1064 – When Syncing #19271
    Ritesh
    Member

    Can you send me the table structure and sample data to reprodce the error?

    in reply to: Feature Request #19266
    Ritesh
    Member

    Can you provide an example to explain the issue a little more?

    in reply to: Cosmetical #19270
    Ritesh
    Member

    Will be done in BETA 3 🙂

    in reply to: Schedule Backup Question #18851
    Ritesh
    Member

    v4.2 BETA 2 has been released that implements the above feature.

    http://www.webyog.com/forums/index.php?sho…63&st=0&p=7278&#038;

Viewing 15 posts - 631 through 645 (of 2,527 total)