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

Forum Replies Created

Viewing 15 posts - 931 through 945 (of 2,527 total)
  • Author
    Posts
  • in reply to: still problems with \ character in PK #18235
    Ritesh
    Member
    Quote:
    You will have it brought to attention of MySQL AB some other way (using your contacts with MySQL ?)

    We are Authorised Gold Partners of MySQL AB. I have already started a conversation with MySQL AB developers on this issue and talks are going on. I will reply here once I get a concrete solution to the problem.

    in reply to: export null #18396
    Ritesh
    Member
    Quote:
    And after all SQLyog 4.06 and 4.07 crashes when it tries to open graphics data that it has inserted itself into a TEXT column! At least it does with latin1 charset (a single byte charset) on MySQL 5.07. And what would happen for instance it you used graphics data with a double-byte character set (Chinese, japanes, Korean)? And will it work too with both ucs and utf and … And with all available storage engines and mySQL versions ?

    This bug has been reproduced by our developers. We are working on it. The next v4.07 BETA will have the bug-fix.

    in reply to: export null #18394
    Ritesh
    Member
    peterlaursen wrote on Jun 25 2005, 09:23 PM:
    One thing more: BLOB-viewer lets you insert graphics into a TEXT-field. It shouldn't! See pic.

    From the MySQL Docs at:

    http://dev.mysql.com/doc/mysql/en/blob.html

    There is no restriction that TEXT column cannot have an image data. As they say:

    Quote:
    BLOB columns have no character set, and sorting and comparison is based on the numeric values of the bytes in column values. TEXT columns have a character set, and values are sorted and compared based on the collation of the character set assigned to the column
    in reply to: export null #18392
    Ritesh
    Member

    I have forwarded the issue to my development team. They will look into it tomorrow.

    in reply to: export null #18390
    Ritesh
    Member
    Quote:
    With text-data there is an almost cosmetical issue: when opening the BLOB-viever, you'll have to click in the window to activate the keyboard with the window.

    Fixed in SQLyog 4.07 BETA 4 development tree.

    Quote:
    graphics is not lookin good! there are som artifacts and proportions are changed. See attached pic.

    This is due to the fact that SQLyog shows the image in the available dimension of the window. The distraction is due to showing a large image in small dimension. Dont worry though – the data inside remains the same.

    Quote:
    would it be a big deal to make the BLOB-viewer window resizable

    Its in the TO-DO list of SQLyog.

    Quote:
    BTW: is it still in the TO-DO list to let BLOB-viewer dislay a binary/hex view of data ?

    Yes.

    in reply to: export null #18379
    Ritesh
    Member

    So are you able to edit the result?

    in reply to: what is the timestamp problem? #18399
    Ritesh
    Member

    The problem is how MySQL handles TIMESTAMP. There is a significant difference between versions prior to v4.1 and as of v4.1.

    You can get more details at http://dev.mysql.com/doc/mysql/en/datetime.html

    We plan to modify SJA to work around the incompatibility in one of the future versions of SJA.

    Quote:
    guess I could also change the column type to say char, do my sync and then change back

    Its a valid workaround as of now. 😉

    in reply to: export null #18377
    Ritesh
    Member

    Bug #1 confirmed and fixed in BETA 3 development tree.

    in reply to: what is the timestamp problem? #18397
    Ritesh
    Member

    SQLyog uses a checksum based algorithm to compare and sync two databases. In the algorithm, the MySQL function concat_ws() plays a very important part. The function is known to return different result across multiple MySQL versions.

    To check for compatibility just execute the following query:

    Code:
    select md5(concat_ws('A','B',''))

    You should get similar results for both your source and target server.

    in reply to: export null #18376
    Ritesh
    Member
    just4fun wrote on Jun 24 2005, 10:17 AM:
    1. ok, bug confirmed.

    2. tell me please, why i can't edit text type field?:

    Code:
    select * from `test`.tablename1 where id in(1,2);

    If you look carefully, the result is still Read Only as shown in the combo box. You have to select the correct table from the combo dropdown to edit the result.

    in reply to: Ver 3.52 Import CSV problem #14816
    Ritesh
    Member

    Just enter \ in SQLyog's CSV Export/Import Escape Character window.

    in reply to: Question and Suggestion about SJA #17876
    Ritesh
    Member

    Its:

    sja.exe test.xml -ltest.log and not sja.exe test.xml -l test.log

    There should not be any space after -l

    in reply to: still problems with \ character in PK #18229
    Ritesh
    Member

    I guess I will need to call up MySQL AB's support team to discuss on this issue. I have no clue why its behaving like this.

    Quote:
    data shown in graphical client (Open Office 2 Base);

    You can use SQLyog for the same purpose 😮

    in reply to: export null #18364
    Ritesh
    Member

    Can you cut-n-paste the create table statement for the table?

    in reply to: Version 4.07 missing from download page #18328
    Ritesh
    Member

    Seems like an issue in our build script. :huh:

Viewing 15 posts - 931 through 945 (of 2,527 total)