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

Forum Replies Created

Viewing 15 posts - 4,126 through 4,140 (of 7,398 total)
  • Author
    Posts
  • in reply to: Utf-8 Sql Errors And Export [help Needed] #24208
    peterlaursen
    Participant

    BTW: 'Query Browser' from MySQL AB and phpMyAdmin does the same. It is a server issue, not a client issue!

    and also BTW: all connection types are affected!

    in reply to: Utf-8 Sql Errors And Export [help Needed] #24207
    peterlaursen
    Participant

    We have now reproduced this '?'mark thing.  But this is reproducable in MySQL 4.1.10 not in 4.1.21.

    It is wellknown that early 4.1.x MySQL builds had bugs in the charset implementatio

     (that were mostly fixed in 4.1.12 only).

    Now the problem is that quite a lot of Linux distros ship with 4.1.10 (RHEL4, Fedora3 for instance).  However there is an official Red Hat version 4.1.20 build if you prefer to use those (and not downloadables from MySQL mirrors).

    Also very early 5.0.x may have similar bugs!

    Conclusion: MySQL bug, not SQLyog bug. You should upgrade MySQL!   😛

    did I ask you about the MySQL version?

    in reply to: Utf-8 Sql Errors And Export [help Needed] #24206
    peterlaursen
    Participant

    We have now tried on 4 different client machines (XP and Vista, English and Danish locales) connecting to different server with all sorts of available connection types – including HTTP.

    The '?'mark issue is not reproducable!

    in reply to: Utf-8 Sql Errors And Export [help Needed] #24205
    peterlaursen
    Participant
    Quote:
    See the screenshots of the sqlyog display. As already said, it does not show the content right.

    But it does for me.  Look at my screenshots!

    I cannot be sure what is the reson that you get '?'marks, but it could be a webserver/PHP related (configuration)issue with cyrillic.  So that is why I would like to know if this happens with HTTP(s) tunnelling only!

    in reply to: Restart Linux Mysql Server From Win2003 #24234
    peterlaursen
    Participant

    no!

    SQLyog connects to MySQL with the C client API.  To restart the server we need shell access (access to the OS and not MySQL).  Just like you cannot lift yourself by pulling your hair, the MySQL server cannot start and stop itself!

    It could be implemented using SSH, however, but there are no such plans.

    in reply to: Feature Request: Sqlyog Tunnel For Windows #24231
    peterlaursen
    Participant

    We have considered ASP/ASP.net, JSP (and maybe even Ruby if practicalble).

    The reason that it has not happened yet is a 'weighing' of resources to develop compared  to the demand.  The tunneller is now a pretty complicated piece of software!

    We have 1-2 months work in finishing what we have startet.  After that we will do some long term planning for the next year or so!

    in reply to: Request For New Features #24230
    peterlaursen
    Participant

    1) giving an option to ave or 'spool' history to a file is a request already registered

    2) what kind of files?  script files saved from the editor?

    in reply to: Utf-8 Sql Errors And Export [help Needed] #24203
    peterlaursen
    Participant

    with real unicode the same exercise (inserting blanks) generates the SQL

    Code:
    update `test2` set `ID`='2',`post_title`='д Ñ� Ñ‚ в о Ñ� Ñ� к о н ' where `ID`='2'

    (and my browser does not render this correctly as cyrillic! But in SQLyog HISTORY it displays correctly!)

    This is real unicode as it was meant to be and as we support it!

    in reply to: Utf-8 Sql Errors And Export [help Needed] #24202
    peterlaursen
    Participant

    At least we are getting closer in understanding one another.

    You store a utf8 string in a table column created as 'latin1'.

    This will NOT be stored as unicode (in the MySQL sense of the word) but it will be stored as 'latin1' and every byte stored will display as the latin1 glyph for that byte value!  (what the docs for this system calls 'semi-unicode)

    If you omit the 'latin1' desriptor for the column like

    CREATE TABLE `test2` (

    `ID` bigint(20) unsigned NOT NULL auto_increment,

    `post_title` text NOT NULL,

    PRIMARY KEY (`ID`),

    KEY `type_status_date` (`ID`)

    ) ENGINE=MyISAM DEFAULT CHARSET=utf8

    then it is real unicode.  

    But with your data you should still be able to edit the 'semi-unicode/latin1' string.  At least inserting spaces (and any ascii-character actually) should work seamlessly (with most other characters there will be a keyboard problem!).  Also copy/pasting should work!

    SQLyog displays data as it is stored in the database.  If it does not there is a

    bug or at least some issue!

    So far I think we agree now!

    But it works for me here.  With both direct connection and HTTP-tunnelling if I insert a blank between everyone of your characters the SQL goes like

    insert into `test`(`ID`,`post_title`) values ( NULL,'Ð ´ Ñ ï¿½Ñ â€š Ð ² Ð ¾ Ñ ï¿½Ñ ï¿½Ð º Ð ¾ Ð ½')

    Also see attached picture.   Row 2 is inserted with direct connection, row 3 with HTTP connection.  Exactly the same.  And exactly the same SQL.  No '?'marks in the SQL or in the data display!

    It would be very nice if you could find some way to establish direct or SSH connection!  

    Is the SQL with '?'marks in it copied from SQLyog HISTORY tab?

    And when you insert blanks you open the text-string in the BLOB viewer an eidt form here (silly question probably – what else?!! But just to be perfectly sure!)

    in reply to: Thanks Sqlyog – I M Now Using Sidu #24227
    peterlaursen
    Participant

    Actually SQLyog runs with Wine:

    http://webyog.com/faq/31_71_en.html

    in reply to: Character Encoding Unicode/utf-8 Problem #24089
    peterlaursen
    Participant

    OK .. I missed that the 'title' filed was a varchar.  As long as you only save single-byte characters that does not make much difference.

    Try to create a table where every column (or the table itself) is UTF8. Ensure tht there are varchar or text columsn(s) in it.  From SQLyog simply enter Vietnamese characters from a Vietnamese keyboard.  Now try dump that table and you will see the Vietnamese characters directly displayed in the dump file (in this situation also the file itself will be encoded with utf8).

    It may be problematic to change!  Probably quite a a lot a changes are required in the web front-end if data stored as Unicode in MySQL shall be displayed correctly as it seems that this web-frontend uses quite another concept!  But give it a try (and ensure that also uft8 encoding is specified in META tags for the web pages)

    peterlaursen
    Participant

    “when I click on the icon for a new register” .. In English we would say 'row' and not 'register'.  No issue .. now I understand.

    In the RESULT tab DEFAULTs do not display when you add a new row.  Confirmed!

    peterlaursen
    Participant

    maybe I understand now!

    You are talking about the RESULT tab and not DATA tab? and you click the + icon to insert a new row?

    peterlaursen
    Participant

    For me defaults display OK here.

    What am I missing ?????? :huh:

    peterlaursen
    Participant

    we have never seen it (of course).  we have of course also located the error message in the source code, but we do not think that helps us much!

    Does it always happen or with certain tables or scripts only?

    Can you attach a sample script and a sample dump to reproduce with?

    Can you try connecting to another server?

    If you have more PC's can you try installing on another?

Viewing 15 posts - 4,126 through 4,140 (of 7,398 total)