Query Windows Do Not Show Line Breaks

[TGKnIght]

Query windows do not show line breaks.. It would be nice…

[peterlaursen]

Could you explain a little bit more … and maybe post a screenshot … tht would ne nice 😀

Or are you requesting some symbol like Greek letter 'pi' in some wordprocessors to indicate the linebreak?

[TGKnIght]

I'm sorry, I should have specified which query window 🙂

Specifically for jobs, when you enter a query to execute, it does not save the line breaks.. i.e. in the XML file there is an invisible /n for a line break… The query window should parse this 🙂

I have attached a screenshot of the query window I speak of..

[peterlaursen]

I would like you to tell HOW you enter that linebreak? Do you key it in from keyboard, or do you copy from some other program?

Windows standard for link break is both characters “rn” or (in ASCII) or (in HEX) “0D 0A”; *nix standard is r only.

With this query

Code:

use test;
select * from my_table;

.. no matter if I key it in or copy from Editor/SQL-pane the saved XML-file has both characters. When opened in NOTEPAD each character displays in each their line.

If you paste in from some editor generating only the n character 'Notifications Services' simply sends and saves it as it was entered. If you open the XML in NOTEPAD all queries will be displayed in one line. However there are lots of other editors and some display a linebreak with the n character only.

And actually on my system the 'Notifications Services' query window displays a linebreak if either of the control characters are present.

Question is: how do you enter the SQL? Looks like you are pasting from a program that strips the control characters?

[TGKnIght]

I either write the query entries directly in the 'Notifications Services' query window or copy it out of SQLyog's normal query window…

The first time when I type it in, or copy it in, it shows the line breaks, however if I go back to edit the query, the line breaks are not displayed when it pulls from the job xml file.

When I view the XML file with my own text editor the line breaks display there correctly.

I have not used my text editor to modify the job files directly, only to view.

[peterlaursen]

Quote:

however if I go back to edit the query, the line breaks are not displayed when it pulls from the job xml file.

Yup! now I understand. Confirmed. Actually both control characters rn are stripped away when loaded into Notifications Services SQL-window from an existing job file. You can copy into a HEX-editor and see that both character '0D' and '0A' are missing. However first time you type it they both are there.

Agree that this should be fixed!

[TGKnIght]

Ok good now we on the same page 🙂

So you are saying the line breaks are stripped only on display..

As I mentioned when I view my job xml file, the line breaks are still present, although they are not when displayed via the notification query window.

[peterlaursen]

What I say is that a sequence of the ASCII control characters (or 'rn' in C-syntax notation or or (in HEX) “0D 0A”) is stripped out somehow, when you load an existing XML file into the wizard.

And as there are not such characters the Notifications SQL Window does not display a linebreak. It displays what data it has!

Try: Run the wizard 'from scratch', write a statement of two lines and copy to a HEX-editor (mark-up with the mouse and use CTRL-C keyboard shortcut to copy to clipboard, netx past (CTRL-V) into HEX-editor). Finish the wizard and save the XML. Next run the wizard again, open the exiting XML, step through the wizard till Notifications SQL window appears and copy again to HEX-editor the same way. Compare the two HEX views. What you copied in the first run has the “0D 0A” HEX sequence (that is a WINDOWS linebreak 'code') – what you copied in the second run has not.

[Ritesh]

Thanks for the bug report. We will work on it today and fix the issues.

[Ritesh]

Bug fixed in BETA 7 development tree. The same bug effected ODBC Import wizard too so we fixed that too.

[Author]

Posts