Department of Workforce Investment
Division of T echnology S ervices
S ystems M anagement B ranch
500 Mero St., C apitol P laza T ower, 9 th Floor, Room # 903
Frankfort , Kentucky 40601
Phone: (502) - 564 - 4980
Fax: (502) - 564 - 9504
Email: KrishnamurthyT.Malyavantham@ky.gov
This has nothing to do with the second line being commented. It’s prompting for
what it thinks is the variable in the first line. SQL*Plus does the same thing.
Besides, variables within quoted strings can be useful (such as when generating
INSERT statements).
This has nothing to do with the second line being commented. It’s prompting for
what it thinks is the variable in the first line. SQL*Plus does the same thing.
Besides, variables within quoted strings can be useful (such as when generating
INSERT statements).
Yeah, I corrected that. The point is: prompting for vars can be disabled for
comments, but not for strings per the reason below. There may be other cases
where variables with strings are desired. If there’s a strong movement to make
this type of variable an option similar to those in comments, then the Idea Pond
is the place to go.
Yeah, I corrected that. The point is: prompting for vars can be disabled for
comments, but not for strings per the reason below. There may be other cases
where variables with strings are desired. If there’s a strong movement to make
this type of variable an option similar to those in comments, then the Idea Pond
is the place to go.
Yeah, I corrected that. The point is: prompting for vars can be disabled for
comments, but not for strings per the reason below. There may be other cases
where variables with strings are desired. If there’s a strong movement to make
this type of variable an option similar to those in comments, then the Idea Pond
is the place to go.