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

Forum Replies Created

Viewing 15 posts - 2,881 through 2,895 (of 7,398 total)
  • Author
    Posts
  • in reply to: #26834
    peterlaursen
    Participant

    1) please try to turn off autocomplete from program 'preferences'.

    2) we have another recent report with very slow operation when locating network folders.

    Some issue seems to be there! it would be nice if you could confirm if it is related ot autocomplete or not (there may be some issue with alias support introduced in 6.5)

    in reply to: #26844
    peterlaursen
    Participant

    I have tried to reproduce that wrong database was exported. I cannot. Nertheless I think I have an idea ..

    What I imagine could be the problem is that the export idalogue has 'memory' of the filename. If you have exported db1 once as 'db1.sql', next you open the dialogue the proposed filename is still 'db1.sql' . It will overwrite (but prompt you to confirm the overwrite though!)

    Do you think it is better that we as defaault 'fill out' the file name wiht the name of the database?

    Or is the problem another?

    in reply to: #26843
    peterlaursen
    Participant

    “It appears that even though I have selected one dump file, it is using another.”

    Please tell:

    1) ” it is using another” the (complete) dump (not only the USE statement) is a backup of another database than what you thought it should be? correct?

    2) “though I have selected” how did you select? by clicking in the Object Broser or using the dropdwon?

    3) did you use the database context-menu in the Objects browser or the menu in the menu line for starting the dump process? Or is it 'scheduled backup' ?

    in reply to: #26765
    peterlaursen
    Participant

    and .. for security we have restricted uploads to common compressed image formats (gif, .jpg, .png), .txt and .zip.

    in reply to: #26764
    peterlaursen
    Participant

    yes .. they can be installed at the same time to different folders. Only you will need to create shortcut(s) manually (shortcuts for 2nd install will overwrite shortcuts for 1st install).

    in reply to: #26832
    peterlaursen
    Participant

    I think we need more info about the type of network! Is it s 'workgroup' type of network, a domain-server-controlled network or something more special (like involving SAMBA shares on Linux)?

    If you use the ip and not the 'machine name' does the same thing happen?

    Maybe if the WinAPI does not return the errror that network is not available then I think it may 'wait forever'.

    in reply to: #26795
    peterlaursen
    Participant

    hi .. could you please check the 7.0 RC release with Wine on your system?

    in reply to: #26824
    peterlaursen
    Participant

    not reproducable for me .. I can copy data like

    1 abc

    2 xyz

    3 æ

    4 ø

    5 å

    6 aæbøcåz

    7 aæøåz

    8 æøå

    … from latin1 tables on 3.23 and 4.0 to a 5.0 server running utf8 as default using 'copy to other'.

    Please provide details of how to reproduce!! You also told about *two* copy methods. Except for *copy to other* what is the other?

    but still I think we have two discussions ..

    * The table TYPE/ENGINE on gets created as the default. Not identical to. I copied a MyISAM table and it became InnoDB on

    * the two servers have different non-unicode charsets (or ifis not) then some warning should come!

    Ideally I think the copy dialogue should have a TYPE/ENGINE and CHARSET option!

    in reply to: #26823
    peterlaursen
    Participant

    One correction: when exporting with SQLyog from 3.x and 4.0 server the DUMP is *not* UTF8-encoded (but ANSI in MS-terminology). Simply because it would not import correctly on that server if it was UTF8! The DUMP will be a *plain binary copy* of how data are stored on the server .. and if your computer is configured with a LOCALE that matches the data you can read them ('æøå' will display like that with ANSI western codepage (only) – but reading them with a computer using another LOCALE/codepage setting will not display them correctly).

    in reply to: #26822
    peterlaursen
    Participant

    “Unfortunately I cannot attach sample dumps…” If you could create a silly example with a single table and a few rows of data to reproduce with that would be fine too!

    In MySQL 3 and 4.0 charset can be defined on the server-level only. Accordingly table definitions in those versions have no CHARSET and COLLATE specification.

    I think (maybe) you are copying to a 4.1+ server using utf8 as default?

    Please try to create the table structure in advance on using latin1 for that table (or the database where it belongs).

    We should not just 'throw away' those characters .. at least some warning should appear. Or we should give user an option to select between 4.1 charsets that are compatible with 3.x/4.0 for the table.

    What information you can provide would help!

    in reply to: #26820
    peterlaursen
    Participant

    Hello .. I am danish too actually .. so i know 'æøå' very well.

    I cannot reproduce the problem – see attached

    [attachment=936:target.jpg]

    I enter those data .. copy to other .. and the table looks the same.

    “iso-8859-1” does not apply to programs like SQLyog – SQLyog is NOT a webpage! SQLyog is a unicode program (from 6.0).

    Please refer to:

    http://webyog.com/faq/content/34/102/en/wh…-by-sqlyog.html

    http://webyog.com/faq/content/34/148/en/do…y-language.html

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

    Please:

    * tell EXACTLY how to reproduce

    * tell were those 'æøå' inserted with SQLyog? or what program/application?

    * dump that table (with SQLyog (or 'mysqldump') .. not phpMyAdmin or whatever because the DUMP needs to be UTF8-encoded), open in Notepad. How does data display here? And please attached such sample dump (zipped please!)

    I figure that this is an issue with the application that originally stored those data. Data are probably not stored as 'æøå' but some client-side encoding is used that the MySQL server knows nothing about!

    Also try upgrade the program (I am using 7.0 beta1)

    in reply to: #26761
    peterlaursen
    Participant

    From 7.0 beta1 we use the query “show full tables” .. before that “show table status”. “Show table status” can be very slow in particular with large InnoDB tables.

    In 6.5 we introduced the 'tree view' in export dialogue what also required lookup for named routines, triggers etc. That gave more 'overhead' in 6.5 as compared to 6.1.

    I think this is the issue – and not related to file system lookup.

    Could you try 7.0 beta (or 7.0 RC that will probably be released later today)?

    in reply to: #26760
    peterlaursen
    Participant

    So we will have to check whether the routines we use to access file system information from Windows were changed in 6.5.

    in reply to: #26817
    peterlaursen
    Participant

    Can you tell what Apache directive it was causing this? That would be usefull for us to know!

    in reply to: #26815
    peterlaursen
    Participant

    Please try a more recent version and try the different HTML content-type options added (in 6.5). First of all try 'urlencode' as this webserver is Apache.

    Changelogs for 6.5: read

    “– For HTTP-tunnel added an option to specify 'urlencode' HTTP header format on a per-connection basis (default is 'text/xml' header format). Using this option can be required if Apache 'mod_security' (as well as some largely undocumented filters and 'hacks') is enabled.”

    Program help file (from 6.5) read:

    “The content-type option was added in 6.5. Most users will not not need to care about this as they most often will all work, but in some situations a special HTTP format is required. Known situations are:

    * With Apache and mod_security extension enabled in Apache configuration it may be necessary to use 'urlencode'

    * With IIS running on Windows Server 2003 some PHP editions will fail to connect with 'urlencode' setting.

    * Open source webservers (like Apache, Lightttpd) may have been built with some code change (or 'hack') blocking certain HTML content-types.

Viewing 15 posts - 2,881 through 2,895 (of 7,398 total)