Copy Data to Clipboard

[caves]

Hello,

First of all Great Product!!!

One thing I seem to have problem with is the Copy Data to Clipoard in the Results Pane. It doesn't remember the last values selected for the escaped characters once I copy some data to the clipboard.

I'm using version 4.0 Freeware Edition

Thanks

[Ritesh]

It should.

I have forwarded the issue to my development team.

[sliderule96]

Using SQLyog . . . Version 4.0 . . .

Great Product . . . . Thank-you

Just want to 'confirm' that file SQLyog.ini values in section of:

[CSVESCAPING]

ESCAPEDBY=

FESCAPE=

ENCLOSEDBY=

are not retained (remembered) from session to session. I hope this can be fixed in the next release.

SlideRule96

[Ritesh]

Thanks for the info.

[tdunning]

This problem occurs with any CSV export operation and it is worse than just not saving values between sessions. Values are lost even during a single session.

This is very annoying and causes data corruption if the user doesn't make absolutely sure that all of the values are correct. Since it is common to export data and then repeat the operation (either on another table or on the same table after a tweak), and since it is very reasonable for the user to presume that the values have been saved, this isn't very surprising. The consequences of not having a line or field delimiter is pretty dire.

This should be a pretty high priority bug.

[Ritesh]

SQLyog 4.01 BETA has been released. It fixes the bug as reported by all of you.

You can download it from:

FREE edition: http://www.webyog.com/sqlyog/SQLyog401.exe

Enterprise Edition: http://www.webyog.com/sqlyog/SQLyog401Ent.exe

Please confirm the bug fix?

We will be releasing 4.01 FINAL later this week.

[caves]

It doesn't work when you use Copy to Clipboard,

It appears to work when you use Export Resultset, but when you use Copy to Clipoard after you it cleans the variables in the .ini file.

This is the .ini after Export Resultset

ESCAPEDBY=

FESCAPE=t

LESCAPE=n

ENCLOSEDBY=”

After Copy to Clipboard (Right after using export resultset)

ESCAPEDBY=

FESCAPE=

LESCAPE=

ENCLOSEDBY=”

Thanks

[tdunning]

I have downloaded the beta and it does seem to work better.

More testing is still in order to fully confirm that this bug has been fixed, but it looks good so far.

[tdunning]

Copy/paste to clipboard doesn't seem to work correctly. The line terminator disappears on me and lines are terminated by a comma. Here are some sample lines of output:

“5376”,”20040818004701″,”20040818004630″,”Nbbdabaacaaa”,”no”,”43″,”0.127811517685480″,”1″,”1″,”1428″,”1″,

“5377”,”20040818005201″,”20040818005117″,”Nbccaaacaabc”,”no”,”45″,”0.108615375225070″,”1″,”1″,”485″,”1″,

“5378”,”20040818005201″,”20040818005146″,”Ndcdcbdaabbb”,”no”,”45″,”0.433942686239200″,”1″,”1″,”588″,”1″,

I don't think that the trailing commas should be there. The confusion may be that the comma should really be a field separator, not a field terminator as is described in the copy to clipboard dialog. In any case, if I repeat the copy to clipboard, the newline character is lost and all of the data appears on one (huge) line.

A possibly related issue is that if I enter the escape character as \, then the next time around it will be listed as . It may be that the n that I have as the line terminator is unescaped the next time around and is then shown as a newline which is just whitespace which gets lost. The correct behavior is to unescape when reading the character from the dialog, but then quote or escape the string when writing to persistent storage. Also, if n is allowed as a line terminator, then \ should be documented as the correct way to express the use of backslash as an escape character.

The summary is that it works better, but it isn't fixed. The bug may have been caused by two problems, one of which is fixed. The old problem of completely losing track is better, but the second problem to do with backslash escaping appears to be unchanged.

[Ritesh]

Thanks for the review. We have fixed the above bugs and released a new build of SQLyog 4.01.

You can download it from:

FREE edition: http://www.webyog.com/sqlyog/SQLyog401.exe

Enterprise Edition: http://www.webyog.com/sqlyog/SQLyog401Ent.exe

Please confirm the bug fix?

If everything is fine, we will be releasing SQLyog 4.01 FINAL by end of this week.

[tdunning]

This bug appears to be resolved as far as my usage is concerned. Escape characters appear to be persistent across sessions for both copy/paste and import and the strange behavior with back-slashes has apparently been tamed.

I have also verified that trailing separators no longer appear.

Thanks very much for the quick fixes.

[sliderule96]

Quote:

Posted on Dec 21 2004, 10:59 PM

Just want to 'confirm' that file SQLyog.ini values in section of:

[CSVESCAPING]

ESCAPEDBY=

FESCAPE=

ENCLOSEDBY=

are not retained (remembered) from session to session. I hope this can be fixed in the next release.

SlideRule96

Just want to confirm, that in my testing, with new build of SQLyog 4.01, the situation appears to be resolved.

Thank-you, and, the team, for a quick response.

My thoughts are with you, the team, and India, with regard to the Tsunami disaster.

SlideRule96

[Ritesh]

Thanks for your concern.

Tsunami effected south-eastern coastal areas of India. We are located in Bangalore which is situated in south-central part of India away from the coast. We are doing great and working toward SQLyog 4.1.

[caves]

Thanks,

The bug is resolved in my tests also.

It's working great!!!

Looking forward to 4.1

—

caves

[Author]

Posts