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

Forum Replies Created

Viewing 15 posts - 5,896 through 5,910 (of 7,398 total)
  • Author
    Posts
  • in reply to: Could Not Connect To Source Mysql Server #19790
    peterlaursen
    Participant

    and use the local ip (ie. 10.0.0.1 or whatever and not 127.0.0.1) I would add. Or some name server alias for that.

    in reply to: Could Not Connect To Source Mysql Server #19789
    peterlaursen
    Participant

    QUOTE
    I used the MySQLdb module which is the Python API for accessing mysql

    Well I don't know if it uses socket or TCP. But you seem to know.

    QUOTE
    # Instead of skip-networking the default is now to listen only on

    # localhost which is more compatible and is not less secure.

    bind-address = 127.0.0.1

    Could I suggest that you try comment out like

    QUOTE
    #bind-address = 127.0.0.1

    That would implement MySQL standards which are 'not skip_networking'

    127.0.01 may be routed over socket with that system.

    QUOTE
    which is more compatible

    Compatible with what? Not MySQL standards!

    in reply to: Could Not Connect To Source Mysql Server #19787
    peterlaursen
    Participant

    You don't answer my questio, I believe!

    QUOTE
    Can you connect with some other client using the C-API, such as *MySQL Administrator* ?

    I am not talking about commandline! Clients that connect through socket are irrelevant here! It must be a client using TCP for connection!

    In your my.cnf does it read like

    skip_networking

    or

    #skip_networking

    …if it is 1st then TCP connections are disabled.

    Also: do you have any firewall application running?

    in reply to: Automate The Import Of .txt Files #20566
    peterlaursen
    Participant
    Quote:
    In the full version when I change the mapping will it apply to all sources?

    Yes this is a restriction with the demo version. It lets you only import one table at a time.

    And I verified this myself recntly with the cutomer data that I wrote about. 196 (to be exact) files imported with one job. It ran for 11 hours on a 1.5 Ghz computer here – while I was sleeping most of the time. ๐Ÿ˜€

    in reply to: Automate The Import Of .txt Files #20564
    peterlaursen
    Participant

    Correction: it is the button named 'Definer format' that opens the delimiter setting et. al.

    in reply to: Automate The Import Of .txt Files #20563
    peterlaursen
    Participant

    The M$ text-ODBC driver does not have all the options that SQLyog CSV-import have. You have the configuration options available from the Windows ODBC-manager. However it should recognize tab-delimited files when configured correctly. Try the settings -button in ODBC-maanger (see screenshot – in my language (Danish) it is 'indstillinger')

    Quote:
    SQLyog is not recognizing the tab delimited format

    Wrong. It is the ODBC driver that does not recognize! But did you configure it?

    in reply to: Howto Rename Database… #20541
    peterlaursen
    Participant

    Holy Cow!

    MySQL changelogs for 5.1.7 http://dev.mysql.com/doc/refman/5.1/en/news-5-1-7.html

    Quote:
    Added the RENAME DATABASE statement.

    http://dev.mysql.com/doc/refman/5.1/en/rename-database.html

    Quote:
    RENAME {DATABASE | SCHEMA} db_name TO new_db_name;

    This statement renames a database. It requires the ALTER and DROP privileges for the database, and the CREATE privilege for the new database. RENAME SCHEMA is a synonym for RENAME DATABASE.

    When the server receives this statement, it creates the new database. Then it moves tables and other database objects such as triggers to the new database. It also updates the Db column in the system tables for objects such as stored routines and events. Finally, the server drops the old database.

    RENAME DATABASE does not change any account privileges listed in the system tables.

    This statement was added in MySQL 5.1.7.

    FAQ updated accordingly: http://webyog.com/faq/28_91_en.html

    in reply to: 5.1.6 Coming #20529
    peterlaursen
    Participant
    in reply to: Turkish Characters #20379
    peterlaursen
    Participant

    I came across this report at mysql.bugs:

    http://bugs.mysql.com/bug.php?id=17473

    It does not explain all of of it (and not at all the HTTP WRITE issue I think) – but there ARE lots of problems with Turkish characters!

    in reply to: Automate The Import Of .txt Files #20561
    peterlaursen
    Participant

    Absolutely YES! ๐Ÿ™‚

    You will need to use the SQLyog Enterprise version (demo available). You can the use the Migration Tool with the Microsoft text-ODBC-driver. It will recognize each supported file (.csv, .txt and maybe more – don't remember exactly) in the same folder as a 'table'. If the data from all files have identical structure and shall be imported into ONE MySQL table, you may configure the Migration Tool (with the wizard) not to empty the table for each file to import.

    Check it and play around with it a little … You must ensure the the text-file format can be read correctly by the ODBC-driver!

    If you need it I can paste in the most important pasages from a SJA XML file to use. I have such sample somewhere on my system from a customer importing about 2 GB's of data from around 200 CSV-files at regular intervals. This job ran for some hours on my system ๐Ÿ™‚

    You may also read: http://www.databasejournal.com/features/my…p/10897_3550146. A few more options have been added to the tool with later versions but it is still basically the same.

    And finally be aware of this issue with the driver: http://webyog.com/faq/17_88_en.html

    in reply to: Now Come On … #20140
    peterlaursen
    Participant

    Updated info:

    DarWINE has been updated to 0.97 (and Wine itself is now 0.98, so probably a DarWINE 0.98 is comming soon too). Refer to: http://darwine.opendarwin.org/

    Note that there is now support for both PPC- and x86- Mac hardware.

    There MUST be someone out there who can test it with SQLyog?

    in reply to: Could Not Connect To Source Mysql Server #19785
    peterlaursen
    Participant

    I really doubt this is related to on which 'nix' dialect it was built. since it has no dependencies and is statically linked. Rather I think it is related to the way MySQL is configured with the actual build (ubuntu in this case).

    Can you connect with some other client using the C-API, such as *MySQL Administrator* ?

    I don't know ubuntu (and what type of install packages it uses) but is a big deal to uninstall the distro-version of MySQL and install/compile a standard build from mysql.com? If you can do this I suggest you try it.

    But I agree that a list of distro's in which it has been tested (with any sort of tricks and configuration issues) could/should be maintained. As the maintaneer of the Webyog FAQ that must be my job! But I will need then that users are more responsive. People don't seem to realise the importance of reporting ร‚ยดnot-problems' – only problems! And BTW: this applies to SQLyog running on WINE as well.

    in reply to: Connecting Error #20559
    peterlaursen
    Participant

    Prot 3306 open is sufficient.

    a google search:

    http://www.google.com/search?client=opera&…=utf-8&oe=utf-8

    http://forums.mysql.com/read.php?45,61565,66934

    Looks like a problem with the C-API on that specific configuration.

    Please read: http://webyog.com/faq/1_26_en.html

    could you answer those questions ?

    Also can you give temporary access to the server=

    in reply to: Sensitive To Values? #20519
    peterlaursen
    Participant

    http://en.wikipedia.org/wiki/Base64

    I linked to it before. It describes base64-'dialects'

    “UTF-7 introduced a system called Modified Base64. This data encoding scheme is used to encode the UTF-16 used as an intermediate format in UTF-7 into printable ASCII characters. It is a variant of the base64 used in MIME. UTF-7 was intended to allow use of unicode in e-mail without using a separate content transfer encoding. The main difference it has versus the MIME variant base64 is that it does not use the “=” symbol for padding, as that character tends to require a fair amount of escaping. Instead, it pads the octet bits with zeros.”

    looks like an issue with the MIME and UTF7 base 64 'dialects' ??

    in reply to: Can't Convert Myisam To Innodb #20557
    peterlaursen
    Participant

    Maybe InnoDB is not enabled with the server configuration?

    SGLyog menu .. tools .. show .. variables. Check for 'has_innodb' system variable. And in some of the 'bundled' LAMP/WAMP distributions innobd is not available at all. Also some ISP's disable it.

    You will need to provide more info about the server!

Viewing 15 posts - 5,896 through 5,910 (of 7,398 total)