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

Forum Replies Created

Viewing 15 posts - 6,181 through 6,195 (of 7,398 total)
  • Author
    Posts
  • in reply to: Connection To Localhost Failed #19942
    peterlaursen
    Participant

    I think I got it.

    You have this in the jobfile:

    Code:

    You specified a two-way sync. Try 'no' instead of 'yes'.

    There must some data in 'timestamp' table that exist in target that don't exist in source. With a two-way sync they will be written to the source. Was that it?

    in reply to: Connection To Localhost Failed #19941
    peterlaursen
    Participant

    Thanks for your report.

    I'll try to understand that and write up our FAQ accordingly!

    I don't understand exactly what you write on the privilege problem on table 'timestamps'

    If the error message relates to the source: that is strange! Did you specify a one-way sync?

    NB: Edited!

    in reply to: Sqlyog Alter Table Bug #19929
    peterlaursen
    Participant

    Confirmed fixed 😀

    in reply to: Small Gui Bug In Alter Table #19965
    peterlaursen
    Participant

    Confirmed fixed! 😀

    in reply to: Mysql 5.1 And Sqlyog. #19962
    peterlaursen
    Participant
    in reply to: Connection To Localhost Failed #19938
    peterlaursen
    Participant

    And …

    did you try another client (such as MySQL Administrator) to check whether this one is able to connect on TCP-IP/localhost

    And more

    'localhost.localdomain localhost' is not a valid URL at all! ther can't be blanks in an URL. 'localhost.localdomain localhost' get interpreted as 'localhost.localdomainlocalhost' . That will be solved by putting them in each their line!

    You can map as many URL's to ip 127.0.0.1 as you like – but only one per line!

    If you have a webserver running then you can try if you can connect to it with [url=”http://localhost”%5Dhttp://localhost%5B/url%5D as the URL. If you can't then your computer does not know any 'localhost'.

    in reply to: Connection To Localhost Failed #19937
    peterlaursen
    Participant

    And …

    did you try another client (such as MySQL Administrator) to check whether this one is able to connect on TCP-IP/localhost

    in reply to: Connection To Localhost Failed #19936
    peterlaursen
    Participant

    This is the problem I believe

    Quote:
    127.0.0.1 localhost.localdomain localhost

    did you read the FAQs that I linked to?

    one of them described the 'localhost.localdomain' issue

    try reversing things to read 127.0.0.1 localhost localhost.localdomain

    also try testing with 127.0.0.1 localhost only

    and put the two in each their line!

    like

    127.0.0.1 localhost

    127.0.0.1 localhost.localdomain

    (I never saw two URL's on one line in a hosts' file before!)

    I think you are turning things upside down when you write:

    Quote:
    i tried to change 'localhost' to 127.0.0.1

    . You 'map' or 'assign' 'localhost' to ip '127.0.0.1'

    127.0.0.1 is ALWAYS your local machine. 'localhost' is only if host file says so and it is read correctly!

    This is not relevant either I believe

    Quote:
    phpmyadmin works perfectly

    phpMyAdmin probably connects through socket, not TCP-IP.

    did you try using '127.0.0.1' as host name instead of 'localhost' in the jobfile ??

    and did you try the ip on the network ?

    BTW: We agree that there should be more logging options! But when not even connection is established there is nothing to log here anyway, I am afraid.

    yeah … I am a developer .. I wrote 48 lines of code 17 years ago. In PPPPL (Peters Private Personal Programming Language), but neither Microsoft, IBM nor Sun would release the API, so I never had it tested! But I still believe it was great 😛

    in reply to: Mysql 5.1 And Sqlyog. #19959
    peterlaursen
    Participant

    In conclusion:

    The 'novelties' of MySQL 5.1 seems to fit fine into the new structure and design of SQLyog 5.x . That makes it quite a lot easer to implement support for MySQL 5.1 then it was with MySQL 5.0.

    Actually the adjustments are minor to get SQLyog work smoothless with MySQL 5.1. But of course it will take time to code support for Partition Management (split partition, merge partitions etc) into SQLyog. But even that does not look frightening. The SQL actually is quite simple and only little GUI work is needed that is not identical or very similar to what is there allready 😀

    in reply to: Mysql 5.1 And Sqlyog. #19958
    peterlaursen
    Participant

    And a small issue

    (and I don't know if it is a SQLyog or MySQl 5.1 issue)

    When copying the 'create statement for the table' from Objects pane there are a lot of blank characters at it end of each line.

    this one

    `id` int(11) NOT NULL auto_increment,

    should be

    `id` int(11) NOT NULL auto_increment,

    but is

    `id` int(11) NOT NULL auto_increment,

    But part of the explanation probably is that the partition part of the statement is one l-o-n-g line.

    in reply to: Mysql 5.1 And Sqlyog. #19957
    peterlaursen
    Participant

    However SQLyog/SJA data sync runs fine between a 5.0.16 and a 5.1.3 table – even if the 5.1.3 table is partitioned! 😀

    MySQL 5.0.16 table definition:

    Code:
    CREATE TABLE `employees` (                      
    `id` int(11) NOT NULL auto_increment,            
    `fname` varchar(30) default NULL,                
    `lname` varchar(30) default NULL,                
    `hired` date NOT NULL default '1970-01-01',      
    `separated` date NOT NULL default '9999-12-31',  
    `job_code` int(11) default NULL,                
    `store_id` int(11) NOT NULL,                    
    PRIMARY KEY  (`id`,`store_id`)                  
    ) ENGINE=MyISAM DEFAULT CHARSET=latin1

    And mySQL 5.1.3 table definition

    Code:
    CREATE TABLE `employees` (
    `id` int(11) NOT NULL auto_increment,
    `fname` varchar(30) default NULL,
    `lname` varchar(30) default NULL,
    `hired` date NOT NULL default '1970-01-01',
    `separated` date NOT NULL default '9999-12-31',
    `job_code` int(11) default NULL,`store_id` int(11) NOT NULL default '0',
    PRIMARY KEY  (`id`,`store_id`)                                                                            
    ) ENGINE=MyISAM DEFAULT CHARSET=latin1
    PARTITION BY LIST (store_id)
    (PARTITION pNorth VALUES IN (3,5,6,9,17) ENGINE = MyISAM,
    PARTITION pEast VALUES IN (1,2,10,11,19,20) ENGINE = MyISAM,
    PARTITION pWest VALUES IN (4,12,13,14,18) ENGINE = MyISAM,
    PARTITION pCentral VALUES IN (7,8,15,16) ENGINE = MyISAM) 

    (note that with a LIST type partition the PK must include the column used for partitioning)

    in reply to: Mysql 5.1 And Sqlyog. #19956
    peterlaursen
    Participant

    There is an issue too with 'copy table to other host'. With this example table definition from the MySQL 5.1 docs

    Code:
    CREATE TABLE employees (
       id INT NOT NULL,
       fname VARCHAR(30),
       lname VARCHAR(30),
       hired DATE NOT NULL DEFAULT '1970-01-01',
       separated DATE NOT NULL DEFAULT '9999-12-31',
       job_code INT,
       store_id INT
    )
    PARTITION BY LIST(store_id) (
       PARTITION pNorth VALUES IN (3,5,6,9,17),
       PARTITION pEast VALUES IN (1,2,10,11,19,20),
       PARTITION pWest VALUES IN (4,12,13,14,18),
       PARTITION pCentral VALUES IN (7,8,15,16)
    );

    copy from 5.1.3 to 4.0.26 works fine (the new 'copy table to other host' -code works here!) – however when copying to 5.0.16 it does not work! (no transformation of the 'create statement for the table' is made). See attached.

    So the new 'copy table to other host' -code needs another extension to faciliate copy to 5.0 (or 4.1 for that sake) from versions higher tha 5.0. However the charset/collation information should NOT be stripped out in this case!

    BTW: the 'create statement for the table' as returned by MySQL 5.1 goes

    Code:
    CREATE TABLE `employees` (
     `id` int(11) NOT NULL,
     `fname` varchar(30) default NULL,
     `lname` varchar(30) default NULL,
     `hired` date NOT NULL default '1970-01-01',
     `separated` date NOT NULL default '9999-12-31',
     `job_code` int(11) default NULL,
     `store_id` int(11) default NULL
    ) ENGINE=MyISAM DEFAULT CHARSET=latin1
    PARTITION BY LIST (store_id)
    (PARTITION pNorth VALUES IN (3,5,6,9,17) ENGINE = MyISAM,
    PARTITION pEast VALUES IN (1,2,10,11,19,20) ENGINE = MyISAM,
    PARTITION pWest VALUES IN (4,12,13,14,18) ENGINE = MyISAM,
    PARTITION pCentral VALUES IN (7,8,15,16) ENGINE = MyISAM);
    in reply to: Http Tunnel I Cannot Connect Says To Me That It Up #19944
    peterlaursen
    Participant

    I am sorry, but I am not able to understand you very well. Does this

    Quote:
    says that it updates.php

    mean that SQLyog Enterprise Trial says that the tunnelling file is not the right version and that you should upload another?

    I think Ritesh will be able to tell you on Monday what error no. 3 is ecatly!

    in reply to: Feature Req: Better Export To Excel #19861
    peterlaursen
    Participant

    The crazy thing is that I don't get the same (Excel 2000. Danish) as vygi does.

    string '000123' is converted to number 123 but number 10.09 is not converted to a date. But M$ might have 'improved' upon this with later versions 😀

    The most annoying thing (for me) is that with OpenOffice Calc (latest developer snapshot) I get exactly what vygi get with his Excel. Grrrr …. 🙁

    There is a detail more: In German and Danish decimal number are written “10,09” not “10.09”. This is implemented in localised Excel-version that way. Vygi: are you using a German Excel or an English Excel and have localised OS-settings only?

    I also believe that it is a further complication, that neither 88.99 nor 10.09 really are numbers in neither German nor Danish! Actually the cells can't be formatted here at all once they are pasted into Excel! Because they are not valid data at all in European localized versions of Excel. formula.jpg illustrates this: you can't add the numbers with a formula when using “.” as decimal seperator. you can when using “,” !!! Nice observation … 😀

    I don't think there is any fix possible as long as copy from clipboard is used. Actually any transfer method using glyphs will fail! The decimal 'dot' must be represented by a symbolic 'decimal dot' (and probably that is what COM does) and no glyph and probably no character number of a charset either! The OpenOfice people have struggled with this locale issue (meaning of “.” and “,” in decimal numbers) for more than a year I know – it was a problem with macros in particular. And it almost split the project: Sun wanted one solution (most possible backwards compability with old StarOffice versions) most of the volunteering participants wanted most possible compability with MS Office.

    So this is not an easy fix!

    in reply to: Connection To Localhost Failed #19934
    peterlaursen
    Participant

    We have a few FAQ entries about this:

    http://www.webyog.com/faq/23_36_en.html

    http://www.webyog.com/faq/16_67_en.html

    … but I shall not claim it is complete.

    We have seen this *nix/localhost issue a few times, but people never reported back if and how they solved their problem. 🙁

    What does your hosts' file say?

    I don't know Debian (I use SUSE) so I can't help you to find it!

    But I believe the info is available from some KDE module on Debian too.

    Do you have any sort of nameserver running ?

    A clever guy remarked once that the 'localhost' mess-up was caused by certain mailer programs when running in server mode. It could also be problems with a ip-forwarding/backlooping setting (any router software installed ?). Firewall ??

    Did you try to use the ip 127.0.0.1 instead of 'localhost'.

    Or the ip of the machine on the network.

    I am also able to use the SAMBA/Netbios name (I am running a SAMBA server in 'primary domain-controller mode'), but implementation may differ with various *nix versions. But on my Linux box, Netbios name simply gets mapped to ip 127.0.0.1 in the hosts' file just like 'localhost' does.

    I am 99% sure that it is a problem that the system cannot resolve the meaning of 'localhost'. Are other clients able to connect to MySQL on 'localhost'? You can try MySQL Administrator or MySQL Query Browser (connect with tcp-ip, not through socket file if both options are available!). And SQLyog for Windows runs under Wine too – you can try this too http://www.webyog.com/faq/5_71_en.html. But I don't think any of them will connect to 'localhost'.

    No solution. But a few things that you could check and think about …

Viewing 15 posts - 6,181 through 6,195 (of 7,398 total)