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

Forum Replies Created

Viewing 15 posts - 3,166 through 3,180 (of 7,398 total)
  • Author
    Posts
  • in reply to: #26051
    peterlaursen
    Participant

    I am now totally confused!

    First I think that ´peq` is a DATABASE and not a TABLE? (just for clarity …)

    You told that the server returned the error

    Quote:
    Query:

    create database if not exists `information_schema`

    Error occured at:2008-03-07 15:31:34

    Line no.:11

    Error Code: 1044 – Access denied for user 'root'@'localhost' to database 'information_schema'

    … then that file MUST contain the SQL statement “create database if not exists `information_schema`”. If not the server messes everything up here! This error message is sent by the server, and what client you use does not matter! You can try 'sourcing' the file from mysql command line (provide that you have a local MySQL installation)

    (copy the file to c: , start command line and “SOURCE c:file.sql”

    [attachment=845:source.jpg]

    (the actual file only contains the statement “create database sourcetest;”)

    Are you sure that you are selecting the right file and path?

    Could you try importing to another server (or let us try?)?

    Try to copy-paste into the SQLyog editor and 'execute all'.

    in reply to: #26049
    peterlaursen
    Participant

    Information_Schema is a system database. It was introduced in MySQL 5.0. It is READONLY. It cannot be written to and thus not restored! Information_Schema content will be created automatically by the server.

    I think you must have backed up Information_Schema database by mistake? Just open the DUMP in an editor and read it!

    You may also attach it here (or create a ticket if you want privacy!). Please ZIP before uploading! The server will not accept .sql files.

    “it's a Table called peq i'm backing up and thats all i had selected when i made backup”. Well, it doesn't look like it!

    What was the SQLyog version you have been using? How do you 'select' what to backup? From the table context menu?

    in reply to: #26041
    peterlaursen
    Participant

    yes .. that is strange!

    if “Click save button” means you are clicking the blue disk icon, it works for me! It saves and the *red* message does not appear again!

    Alternatively you can use or . That will also save.

    You can check in HISTORY what SQL was sent to the server!

    What was the version you upgraded from?

    in reply to: #26037
    peterlaursen
    Participant

    MySQL error 0 is 'MySQL cannot start' I think.

    This is neither a normal client (2000+) nor a server (1000+) error – it comes 'before connection'.

    PHP error 0 is 'no error' (in scripts you may test for it!).

    searches:

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

    Also this only describes the error on Windows (and this is for installation/configuration only:

    Quote:
    If you reinstall or upgrade MySQL without first stopping and removing the existing MySQL service and install MySQL using the MySQL Configuration Wizard, you may see this error:

    Error: Cannot create Windows service for MySql. Error: 0

    This occurs when the Configuration Wizard tries to install the service and finds an existing service with the same name.

    Did you ever do some thing similar to this on this system?

    I don't claim that I have explained everything. I also have no option to test with that Ubuntu and Wine version immediately.

    But we did check our code and verified that this error is not coded into SQLyog but passed from the server.

    Could you try:

    * removing that Wine version

    * reinstalling MySQL (backup the data folder!).

    Also tell does this happen both when running SQLyog (with wine) or that machine and when connecting from another Windows machine (if you have both options)?

    You can try backup with 'mysqldump' (http://dev.mysql.com/doc/refman/5.0/en/mysqldump.html) and 'MySQL Administrator'. I would be *very surprised* if MA (when running from the same host at least) does not throw the same error!

    in reply to: #26035
    peterlaursen
    Participant

    It is the MySQL server that returns this error!

    SQLyog only 'repeats' it.

    Something must have changed on the server side!

    Can you connect normally from the GUI? With other clients?

    On what OS is the server running? There are several reports on the Internet with Windows! Solution is to remove the service from the OS and reconfigure it.

    Try this: http://forums.mysql.com/read.php?11,4460,35804

    (install 'MySQL Administrator', start 'MySQL System Tray Monitor' and proceed as described).

    Maybe also rebooting the server will help (problem is with the service manager).

    I think it happens only with this specific server?

    Server version?

    Exact Windows (or other OS) version?

    We may be able to find more details!

    in reply to: #26033
    peterlaursen
    Participant

    1)

    We are not able to understand or reproduce how export/import fails like this. Can you reproduce this? A small test case (a single table with a few rows) would be nice.

    2)

    data sync/charset issues will be analyzed, fixed and/or documented! But this is not your *original* problem!

    in reply to: #26032
    peterlaursen
    Participant

    It is not commented out!

    /*!40101 …*/ is a 'version dependent conditional comment. This is a MySQL extension to Standard SQl syntax'

    It means “if server is 4.1.1 or higher execute this, if lower handle as comment”. So the SQL is correct! It will be executed!

    But there are some problems with charset and data sync!

    syncing this source

    Code:
    /*
    SQLyog Enterprise – MySQL GUI v6.16
    MySQL – 5.0.51a-community-nt : Database – test
    *********************************************************************
    */

    /*!40101 SET NAMES utf8 */;

    /*!40101 SET SQL_MODE=''*/;

    /*!40014 SET @OLD_FOREIGN_KEY_CHECKS=@@FOREIGN_KEY_CHECKS, FOREIGN_KEY_CHECKS=0 */;
    /*!40101 SET @OLD_SQL_MODE=@@SQL_MODE, SQL_MODE='NO_AUTO_VALUE_ON_ZERO' */;

    /*Table structure for table `aa` */

    DROP TABLE IF EXISTS `aa`;

    CREATE TABLE `aa` (
    `id` bigint(20) NOT NULL,
    `aa` varchar(10) NOT NULL,
    PRIMARY KEY (`id`)
    ) ENGINE=InnoDB DEFAULT CHARSET=utf8;

    /*Data for the table `aa` */

    insert into `aa`(`id`,`aa`) values (1,'abcæøåñäöä');

    /*!40101 SET SQL_MODE=@OLD_SQL_MODE */;

    /*!40014 SET FOREIGN_KEY_CHECKS=@OLD_FOREIGN_KEY_CHECKS */;[/code]

    to this target

    Code:
    /*
    SQLyog Enterprise – MySQL GUI v6.16
    MySQL – 5.0.51a-community-nt : Database – test
    *********************************************************************
    */

    /*!40101 SET NAMES utf8 */;

    /*!40101 SET SQL_MODE=''*/;

    /*!40014 SET @OLD_FOREIGN_KEY_CHECKS=@@FOREIGN_KEY_CHECKS, FOREIGN_KEY_CHECKS=0 */;
    /*!40101 SET @OLD_SQL_MODE=@@SQL_MODE, SQL_MODE='NO_AUTO_VALUE_ON_ZERO' */;

    /*Table structure for table `aa` */

    DROP TABLE IF EXISTS `aa`;

    CREATE TABLE `aa` (
    `id` bigint(20) NOT NULL,
    `aa` varchar(10) NOT NULL,
    PRIMARY KEY (`id`)
    ) ENGINE=InnoDB DEFAULT CHARSET=latin1;

    /*Data for the table `aa` */

    insert into `aa`(`id`,`aa`) values (1,'xyzæøåñäöä');

    /*!40101 SET SQL_MODE=@OLD_SQL_MODE */;
    /*!40014 SET FOREIGN_KEY_CHECKS=@OLD_FOREIGN_KEY_CHECKS */;

    actually syncs. But here log display is wrong it is

    Code:
    Table SrcRows TgtRows Inserted Updated Deleted
    ========================= ======= ======= ======== ======= =======
    `aa` 1 1 1 1 1

    Total time taken – 1 sec(s)

    it should be “1 updated” simply .. or it should refuse to run!

    (and btw if it is identical data with different charset log will tell: (Inserted Updated Deleted) = (1 0 1)

    Ideally I think that

    * syncing two non-unicode charset should be refused

    * syncing a unicode charset to an non-unicode charset should be refused

    * syncing a non-unicode charset to an unicode charset should be allowed

    * syncing two unicode charset should be allowed

    This is a bug I think! But not your problems as the characters you use will work work with latin1 as well as uft8!

    anyway reported here: http://code.google.com/p/sqlyog/issues/detail?id=577

    I also think you found the solution with your application.

    But I am not able to figure out what went wrong in the first place. Why did the SET NAMES statement and the latin1 definition not ensure that data were decoded and inserted correctly? It looks like the server failed here. But server versions are reasonable up to date. Maybe I am missing something. You did not edit the SQL file? Can you build a small test test and reproduce this?

    We will discuss this tomorow!

    in reply to: #26030
    peterlaursen
    Participant

    I will have to think a little about this!

    But ..

    1) OK .. your original data were latin1

    2) But no matter how data are stored on the database, a SQLyog DUMP will use utf-8 encoding (only with 'scheduled backup you can select any encoding).

    2) the DUMP however will have statements “SET NAMES = utf8” and “.. CHARSET latin1” definition for every database or table. (Please check this!) So it should create latin1 tables and 'resolve back' the utf8-encoding to latin1. What is the exact server version? Very early 4.1 and 5.0 versions may have bugs here!

    3) I am 99% sure that there is nothing (intentional at least) changed here between 6.14 and 6.16

    4) I dont know this FLASH software. It seems to have a problem with utf8.

    5) I suggest you do this (to resolve now): simply use data sync to trnasfer the data (you need to create an empty database first).

    If data sync will let you sync data with different charset/encodings, I think it is a 'flaw'. You cannot sync Chinese data to a latin1 database/table. It will become garbage. We will check this tomorrow.

    in reply to: #26028
    peterlaursen
    Participant

    If you still have the SQL file you could check if CHARSET specification is there?

    If data sync worked then the table definitons are the same. If not data sync will refuse to run!

    I do not exclude the possibility of a server error, but not a SQLyog bug either!

    So this is a little bit weird. I think I will have to ask for such dump if I shall be able to figure out exactly what went wrong here!

    (a small one please – but one where it is reproducable)

    Utf8 and latin1 will do equally good as long as only western characters are there.

    What does

    Code:
    SHOW VARiABLES like '%character%';

    from both hosts return (“USE the actual database” first) ?

    in reply to: #26034
    peterlaursen
    Participant

    Currently you will have to edit the .js.

    There is a indicator for changed .js components. Those you should back up before upgrading.

    To support GUI operations we will need some parser component and/or the .js should be divided into more database fields (currently everything is just a single BLOB field).

    We will add to our TODO and consider how to implement!

    in reply to: #26026
    peterlaursen
    Participant

    I will try to make a little simpler to understand what happend.

    Compare “Elías Piña” with “ElÃas Piña”. You will see that accected/non-ASCII characters – í ñ – each become 2 long – Ãa ñ.

    In utf8 those chararcters – í ñ – are each two bytes long. If you insert those byte patterns in a ANSI (latin1) table each byte will represent a character – and that will become garbage like this.

    With this “I created a database dump and restored this database on a different server using SQLYog (Maybe this was the problem and a possible bug??)” I am perfectly sure that originally data were stored as utf8 but the dump did not contain CHARSET specification. Next you imported on a server having latin1 as default charset.

    What program was used for dumping? I think that if it was SQLyog it must have been a very old version!

    Correcting this can be quite a lot of work. It would be easier to export again WITH charset specification if data are still available, but if you need to correct it can be done as described here:

    http://webyog.com/faq/content/34/152/en/my…-in-sqlyog.html

    Quote:
    However you cannot just change the charset for existing databases and tables once they have been created as non-unicode. That will not change existing columns. Also directly changing every column from latin1 (or whatever) to utf8, will not help. The MySQL server will transform the encoding of existing strings and thus preserve the error.

    You will have to 'push in' a binary (non-encoded) step using binary data types (binary/varbinary/BLO:cool: instead of encoded string types (char/varchar/TEXT).

    So basically what you need to do is to perform changes in two operations like:

    latin1 varchar >> varbinary (or BLO:cool: >> utf8 varchar (and similar for char and TEXT types).

    This you will have to do on every existing string column in every table.

    in reply to: #25976
    peterlaursen
    Participant

    After the release of SQlyog 6.2 beta1 (~1 week) we will try to 'push in' a fix for this.

    We will provide a setting in the .ini like

    Code:
    tags_path = “drive:path”

    … so that that path will be used. Ideally this should be implemented in the installer script, but it may take a little more time.

    in reply to: #26012
    peterlaursen
    Participant
    gofree wrote on Mar 3 2008, 04:00 PM:
    @peterlaursen, what is name server alias and how to find it in CP? Is this the last option to remote connect then?

    -thx-

    I cannot tell as I do not know what CP system your ISP is using!

    Ask the support how to connect to to mySQL from a remote host. It does not matter if the client is SQLyog, or Query Borwser or cmd line.

    in reply to: #26006
    peterlaursen
    Participant

    I have no clue about what QB does. But it does use the C-API!

    in reply to: #26010
    peterlaursen
    Participant

    It really depends on the setup/the routing systems on the remote host.

    For instance I used to have a personal website hosted on surftown.dk (Surftown is a large, popular and low-priced ISP operating in most of Western Europe – Sweden, Denmark, Germany, Netherlands, UK, France). The host to specify for remote MySQL connection is/was 'mydb1.surftown.dk'. On this ISP it was not automatically routed even when the port (3306) was specified. You needed to specify the name server alias for the MySQL server ('mydb1') on their network. Other users might need 'mydb2' or 'mydb4' depending on on what physical server the database for this user is located. This information is available from CP for every user.

    Maybe they allow direct connection from everywhere, maybe only from specific ip's/ip-ranges. Also that differs. Surftown allowed for direct connection from up to 10 ip's only. If you do not have a fixed IP you can register with some dynamic DNS service (like dyndns.dk) to work around this.

Viewing 15 posts - 3,166 through 3,180 (of 7,398 total)