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

Forum Replies Created

Viewing 15 posts - 2,476 through 2,490 (of 7,398 total)
  • Author
    Posts
  • in reply to: #27768
    peterlaursen
    Participant

    SJA for Linux does not support tunnelling (neither HTTP or SSH tunnelling). Only direct connection is supported.

    But I believe that you can establish a SSH tunnel in a console and connect to that tunnel-setup. But not quite sure how. I think we can find someone who can help with this!

    in reply to: #27760
    peterlaursen
    Participant

    Basically you should consider SJA for Linux as an extended service for our SQLyog Enterprise users (even though everybody are welcome to use it). SQLyog Enterprise has a GUI interface for building the jobfiles. That is why documenting the XML-schema has not been priority.

    in reply to: #27754
    peterlaursen
    Participant

    I think we do like 'mysqldump' does. Also we cannot change anything here overnight. Best option is to have 5.32 installed too and use this one when pasting binary data from a dump the way you do.

    But an option to write binary data like “unhex(HEX-vaules)” is probably a possibility.

    Also we could consider an option for a query tab not to encode characters. Actually the BLOB viewer can do both so I think most code is there.

    in reply to: #27751
    peterlaursen
    Participant

    Also I can confirm that this particular table does not export as UTF8-encoded. Probably because the binary data are not valid utf8 data! I think Windows *refuses to*!

    in reply to: #27750
    peterlaursen
    Participant

    This is a 'side-effect' on Unicode implementation with 6.0+. It works with 5.x (and tested with MySQL 5.0.67). But the editor of late versions has problems with binary data: I think it utf8-encodes every character displayed (for binary data it should not *think about* the display!

    In short terms the best I can do is to provide link to 5.32. Download from:

    http://www.webyog.com/downloads/oldies/SQLyog532Ent.exe

    (COMMUNITY version. If you are a registered user and need ENTERPRISE then please create a ticket)

    You can have 5.x and later version installed in parallel to different folders (only you need create shortcuts manually).

    Alternatively you can save the INSERT statement to a file and import from tools …

    in reply to: #27748
    peterlaursen
    Participant

    “your output file is ASCII-encoded”

    There is no ASCII-encoding in my opinion. ASCII characters need no encoding! You mean ANSI?

    With SQLyog from 6.0 dumps are UTF8 encoded (however the 'scheduled backup' 'powertool' has an option to select any encoding supported with MySQL) if server is 4.1+. If server is 4.0- the dump is a plain binary copy of what is stored on the server. But binary data are not encoded with any server version.

    We will continue analyzing this tomorrow.

    in reply to: #27746
    peterlaursen
    Participant

    We also tried those 3 programs with same result now! We are analyzing where 'the chain breaks'. Maybe it is an issue with Windows clipboard itself. I have asked our test engineers to try this (but you can do too):

    1) open dump in SQLyog editor tab

    2) copy an INSERT with binary data to clipboard

    3a) open one more editor tab, paste here and execute.

    3b) also try avoid using clipboard at all. Just open the dump in SQLyog editor and execute that single statement!

    Recent Scintilla libraries (we use Scintilla library for the SQLyog editor) should handle non-utt8-valid byte sequences (they claim so!)

    in reply to: #27744
    peterlaursen
    Participant

    “(I'm using Notepad++)” Please first try another editor . Not sure about Notepad++ but it may garble byte sequences that are not valid utf8 sequences! Opening binary data in a text editor is a problem if the data are not valid text data (what they rarely are). Some program handle it – some don't!

    I recommend PSPAD if you do not like Notepad. We will check this too of course! But maybe only tomorrow .. everybody are hung up now!

    in reply to: #27758
    peterlaursen
    Participant

    You should have A PRIMARY KEY in the table!

    Refer to: http://webyog.com/faq/content/28/70/en/i-o…he-database-why

    Please search a little more before asking questions. This was asked and answered at least 20 times before!

    in reply to: #27757
    peterlaursen
    Participant

    1)

    “but in my backup file it does not wrap, it is just one very long line.” That depends on the settings of the editor where you display it. It is NOT an issue with the file! It is a program setting only! In SQLyog the setting is in tools .. preferences .., In Notepad in view …

    2)

    “Additionally, I note that my friends backup file does not have the column names in the insert statement like mine does. Any idea why” because that was changed between the versions! Now 'export' generates socalled '*complete* INSERT statements'. In 5.x it did not! The 'scheduled backup' (ENTERPRISE) 'powertool' has both options since early 6.x versions.

    Please search here for program changes: http://webyog.com/faq/content/33/7/en/sqly…on-history.html

    in reply to: #27756
    peterlaursen
    Participant

    1)

    There should not be any issues with MySQL servers 5.0.41/5.0.45! But I cannot guarantee that there is no bug in 5.0.41, of course!

    2)

    “Why does his backup have no version comments.” Because we did not use this in 5.02 yet

    3)

    version 5 is an ANSI program, version 6 is a UNICODE program. In version 6 we

    /*!40101 SET NAMES utf8 */;

    .. and encode the dump using UFT8, so if the server has utf8 as default charset, the DUMP from a SQLyog5 will not restore special characters correctly. However after adding

    /*!40101 SET NAMES latin1 */;

    on top of it it should!

    4)

    This is strange

    “Additionally, my backup file will not restore and hangs up on his computer with the following line

    /*!50001 DROP VIEW IF EXISTS `viewracedetail` */;”

    .. if he executes that statment manually what happens? One important detail is that if his server was installed 'on top' of a 4.x version he will have to execute the 'mysql_upgrade' program to update system tables (running the installer alone will not do! Refer to MySQL documentation on how to upgrade the server)

    Also please observe that we *in priciple* support only latest stable version. *in practice* we are more flexible, but 5.02 is 3 years old now and that is very long time in software industry! But anyway the most serious problem here is 4) I think, and I doubt that is a SQLyog problem! You can try executing the statement with command line client or whatever!

    in reply to: #27725
    peterlaursen
    Participant

    If you are 'Frank Brewer' who purchased 2007-11-24 you still have free upgrades (you have for a year).

    To upgrade just start here: http://webyog.com/CustomerArea

    (use the email used for purchase as the login ID and also observe that 7.x use a new registration code that you can also get from in there)

    in reply to: #27724
    peterlaursen
    Participant

    Schema Designer printing was introduced in 6.5

    in reply to: #27742
    peterlaursen
    Participant

    “… copy a single INSERT statement to the clipboard and try to run it in the SQLyog query window, the data will be inserted without errors, but the BLOB fields are messed up afterwards.”

    Could you attach a small table dump (please zip) to reproduce this with? A single table with a couple of rows is enough!

    in reply to: #27736
    peterlaursen
    Participant

    ok .. and when you download with some other SFTP client there is no issue that download slows down and excessive memory is used? For instance connect with Konqueror and copy file to a local folder.

Viewing 15 posts - 2,476 through 2,490 (of 7,398 total)