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

Forum Replies Created

Viewing 15 posts - 2,806 through 2,820 (of 7,398 total)
  • Author
    Posts
  • in reply to: #27071
    peterlaursen
    Participant

    We will try to reproduce this, however please tell

    1) model of graphics card(s)

    2) graphics driver version

    in reply to: #27060
    peterlaursen
    Participant

    request added to issue tracker here:

    http://code.google.com/p/sqlyog/issues/detail?id=821

    in reply to: #27064
    peterlaursen
    Participant

    The problem is that there is *no such thing* like 'a SQL statement for dumping the database'!

    Backup is basically *not implemented in the server* – it will have to be *implemented in client code*!

    That is true for SQL dumps, other options are explained here:

    http://dev.mysql.com/doc/refman/5.0/en/backup.html

    (and SQLyog backups are in this context comparable with 'mysqldump' backups – only SQLyog will store on the client machine – not the server machine)

    So either

    * you will have to code a backup routine yourserf (like most standard webapplications do). You will find lots of PHP applications doing it .. but be aware that licenses are mostly is GPL and you cannot copy if if not your applciatoion is licensed with GPL (and often they are not very good!)

    * users will have to use another client – like SQLyog – for backups

    * you can purchase a SQLyog OEM license for distributing SQLyog with your application. We an also find a solution for SJA (SQLyog Job Agent) alone

    That said:

    1) early MySQL versions had a 'backup database' command (working with MyISAM tables only – it simply copied the database files)

    2) and also MySQL plans such feature for MySQL 6.0 (implemented server-side). I am not sure about the details of 6.0 implementation – only this will be more or less a MySQL ENTERPRISE only feature (the MySQL COMMUNITY server will have limited support for it – but I do not believe that is frozen yet in every detail).

    in reply to: #27062
    peterlaursen
    Participant

    and btw: please upgrade!

    in reply to: #27061
    peterlaursen
    Participant

    In SQLyog you should use the GUI (database/table menu or context menu (OR the scheduled backup 'powertool' of the ENTERPRISE editon)).

    You cannot backup a database with a single SQL statement. And also the question is basically wrong as it is the *server* that executes SQL and not the *client* (SQLyog).

    Simply right-click the database in the Object Browser and select 'Backup as SQL dump' and next select the objects and appropriate options (in particular be careful to understand the option to include USE or not in the dump).

    If you want to create a script for unattended backup you should use the scheduled backup of the ENTERPRISE editon. Refer to program documentation and this FAQ http://webyog.com/faq/content/24/82/en/how…ackup-work.html for details.

    in reply to: #27058
    peterlaursen
    Participant

    We have been discussion this before (quite some times actually). The current implementation is described here:

    http://webyog.com/faq/content/8/147/en/how…light=execution

    When that was changed last time we asked users here in Forums we did but had very little feedback!

    I understand that you request some indicator displaying *while executing* – not only *after finishing the query* (like “query executing for 5-10-15 etc. seconds”). Please confirm my understanding!

    in reply to: #27018
    peterlaursen
    Participant

    Please have a look here:

    http://www.webyog.com/blog/2008/08/01/mony…-been-released/

    I think the bug with “ALL” log file chunk size could have been your problem. Please try again after an update.

    in reply to: #27056
    peterlaursen
    Participant

    1)

    SQLyog in not for server monitoring. Our MONyog product is. MONyog has both processlist monitoring and log analysis.

    2)

    Query and Schema analysis and optimisation is something we are considering. We have not decided in what context yet. However MONyog processlist monitoring already has an interface to EXPLAIN (EXTENDED) SELECT … But currently we do no provide advisors from the returns of EXPLAIN though.

    in reply to: #27052
    peterlaursen
    Participant

    Expected timeframe is one week. OK with you?

    in reply to: #27046
    peterlaursen
    Participant

    We are listening and will discuss.

    But on *the very top* of http://www.webyog.com/en/ you will find headers 'What is SQLYog' and 'What is MONyog'. How can we possibly put it higher level than at the very top of our entry webpage?

    I also think that it is very common that company&contact information is available from an 'about' link on a top- of left-side -menu. So much common that I think it is a de facto standard for commercial websites!

    in reply to: #27045
    peterlaursen
    Participant

    ok ..

    * How do you connect to the remote server? direct/HTTP/SSH?

    * How is you BULK (and CHUNK if TTP tunnelling is used) setting in the program

    * And first of all what is the SQLyog version? If not recent please try latest (7.01)

    in reply to: #27043
    peterlaursen
    Participant

    Please tell:

    1) are there duplicate/identical rows in the2) does table have a Primary Key? Please paste the CREATE STATEMENT for the table (copy from SQLyog OBJECTS tab).

    3) it is *exactly* the same dumber of rows that get copied every time?

    in reply to: #27042
    peterlaursen
    Participant

    Did you ever read the MySQL docs on BIT:

    http://dev.mysql.com/doc/refman/5.0/en/numeric-types.html

    and an interesting link here:

    http://www.xaprb.com/blog/2006/04/11/bit-values-in-mysql/

    To insert a BIT valaue correctly the SQL should be like

    INSERT INTO mytable (bit0type) values (b'0')

    or

    INSERT INTO mytable (bit8type) values (b'11011010') .. or what is equivalent INSERT INTO mytable (bit8type) values (x'6A')

    Using *decimal* numbers will insert wrong values!

    Try this

    Code:
    CREATE TABLE `bbb` (
    `id` int(11) NOT NULL auto_increment,
    `b1` bit(1) default NULL,
    `b2` bit(4) default NULL,
    PRIMARY KEY (`id`)
    ) ENGINE=InnoDB AUTO_INCREMENT=4 DEFAULT CHARSET=utf8;

    insert into bbb (b1,b2) values (1,1001);
    show warnings; — Warning 1264 Out of range value adjusted for column 'b2' at row 1
    insert into bbb (b1,b2) values (0,1001);
    show warnings; — Warning 1264 Out of range value adjusted for column 'b2' at row 1
    insert into bbb (b1,b2) values (b'1',b'1001');
    show warnings; — empty set
    select hex(b1), hex(b2) from bbb;
    /* returns

    hex(b1) hex(b2)
    ——- ——-
    1 F
    0 F
    1 9 */

    select bin(b1), bin(b2) from bbb;
    /* returns

    bin(b1) bin(b2)
    ——- ——-
    1 1111
    0 1111
    1 1001 */

    select b1, b2 from bbb;
    /*
    prints the character representation for the binary value if such exists .. for hex(00) it prints 'binary/image'.

    Explanation:
    As SQLyog does not support BIT as a special numercial type, it assumes it is a string and if hex(00) occurs in a string it must be a binary string!
    */

    So there is an issue, bit not *so simple* ! BIT is a numerical type, right – but it will have to be represented in binary or hexidecimal notation!

    in reply to: #27041
    peterlaursen
    Participant

    We know that our support for binary data is not very good.

    Refer to: http://code.google.com/p/sqlyog/issues/detail?id=15

    I hope we can find resources to improve on it soon.

    I have a comment to this “Since the column simply contains a numeric value, SQLjoy could perfectly well show it.” though.

    A MySQL BIT type is a numerical type using the *binary* number system and not the *decimal* number system. I know no client that handles it. ALso MySQL command line does not. Also note in particular that MySQL BIT is NOT a SQL BOOL(ean) type (a common misunderstanding!)! It is also quite different than a SQL Server BIT type for instance.

    A BIT is alos not just a BIT – it has a length. there is BIT(1) and BIT(64). BIT was introduced in MySQL 5.03. Before that BIT (and BOOL) was synonym wiht a TINYINT. Most applications still use a TINYINT. Everybody has problems using the MySQL BIT implementation – and therefore practically nobody does.

    Also to display BIt as a sequence of 0's and 1's would fail when updating because it is *BINARY* 0/1 and not *DECIMAL* 0/1. (try yourself an UPDATE table (bitcolumn) values (a-decimal-number) !)

    Best solution I can think of is that I think we should provide an option to display it as ” b'0' ” or ” b'1' ” (for a BIT(1)) and like ” b'11001101' ” (for a BIT(8)). That would also save correctly when updating. And then we could also support ” x'AE1F27' ” for hexadecimal notation for binary data.

    But I still recommend to continue using a TINYINT with MySQL if you need a boolean!

    in reply to: #27012
    peterlaursen
    Participant

    I understand after selecting a small chunk size it finishes in resonabel time. Please correct me if I am worng!

    Isn't there a 'show details' link? It will display timestamp for last occurance of the query (I think .. right now I am out of town and don't use my own computer)

    EDIT: 'somebody' from our organisation pinged me and told that this option was in 2.5(1).

    Some early *non-public* betas had a display of 'last occurrance time' for the query.

    But with count > 1 it was incorrect so it was never released for the public.

    My memory failed here!

    We are working on a better implementation. Can you tell what you would find reasonable / what you need? Will 'last occurrance of the query' do ?

    Or do you require a complete list of all occurrances? or even a graphical display of the distribution in time (like in history/trends)??

Viewing 15 posts - 2,806 through 2,820 (of 7,398 total)