Wednesday, March 28, 2012

Is there a line feed bug in QA?

Hi,
I am having a heck of a problem on 2 machines (2k & XPPro). SQLServer
2000SP4
Query Analyzer keeps giving me problems and I lose hours tracking down the
problem.
Now I don't know exactly what QA is doing, but I do know that QA will show a
line break, but the proc is behaving as if the line break is not there.
For example, this will not work process the line following the comment;
-- comment
Exec sp_dosomething
But this will
/* comment */
Exec sp_dosomething
Does anybody know of a solution for this?
Thanks,
JohnYou might want to try find one CHAR(13) or only CHAR(10). A proper line brea
k is CHAR(13) +
CHAR(10), aka CRLF. I recall some natyiness if you only had one of those and
not the other, where QA
would display as line break but it didn't behave like a linebreak.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"John MacIntyre" <pls@.reply.here.com> wrote in message news:eMdmLv9wFHA.2540@.TK2MSFTNGP09.p
hx.gbl...
> Hi,
> I am having a heck of a problem on 2 machines (2k & XPPro). SQLServer 200
0SP4
> Query Analyzer keeps giving me problems and I lose hours tracking down the
problem.
> Now I don't know exactly what QA is doing, but I do know that QA will show
a line break, but the
> proc is behaving as if the line break is not there.
> For example, this will not work process the line following the comment;
> -- comment
> Exec sp_dosomething
> But this will
> /* comment */
> Exec sp_dosomething
> Does anybody know of a solution for this?
> Thanks,
> John
>|||Hi John,
I had this same problem, where my script would never enter a while loop
because it thought it was a comment.
All i did in the end was delete all white space near the affected area, so
that all the text is joined, then just add the line breaks back in manually.
Ben
"John MacIntyre" <pls@.reply.here.com> wrote in message
news:eMdmLv9wFHA.2540@.TK2MSFTNGP09.phx.gbl...
> Hi,
> I am having a heck of a problem on 2 machines (2k & XPPro). SQLServer
> 2000SP4
> Query Analyzer keeps giving me problems and I lose hours tracking down the
> problem.
> Now I don't know exactly what QA is doing, but I do know that QA will show
> a line break, but the proc is behaving as if the line break is not there.
> For example, this will not work process the line following the comment;
> -- comment
> Exec sp_dosomething
> But this will
> /* comment */
> Exec sp_dosomething
> Does anybody know of a solution for this?
> Thanks,
> John
>|||Hi
If you open the script in an editor such as textpad you may see some
non-printing character(s).
John
"John MacIntyre" wrote:

> Hi,
> I am having a heck of a problem on 2 machines (2k & XPPro). SQLServer
> 2000SP4
> Query Analyzer keeps giving me problems and I lose hours tracking down the
> problem.
> Now I don't know exactly what QA is doing, but I do know that QA will show
a
> line break, but the proc is behaving as if the line break is not there.
> For example, this will not work process the line following the comment;
> -- comment
> Exec sp_dosomething
> But this will
> /* comment */
> Exec sp_dosomething
> Does anybody know of a solution for this?
> Thanks,
> John
>
>

No comments:

Post a Comment